Skip to main content

Application Server Configuration

Essential customizations (e.g. directories, memory) of the MIMB Application Server can be performed in the following configuration file:
$MIMB_HOME/conf/conf.properties

Recommended customizations include:

  • M_BROWSE_PATH to browse local and mapped network drive.
    All metadata harvesting file and directory parameters references are relative to the server. The reason is that the server must have access to these resources anytime another event (e.g., scheduled harvest) is to occur. On installation, it includes all directly attached drives However, as it is a service, the drive names and paths may vary from what the installer understands, and these drives are not made available at installation time, and thus will not be see when selecting drives using the UI. Note that this also applies and even script backup and restore drives.
  • M_DATA_DIRECTORY to relocate the data such as the log files, and metadata incremental harvesting cache as needed for very large DI or BI tools.
  • M_JAVA_OPTIONS to increase the maximum memory used by java bridges during the metadata harvesting of very large DB, DI or BI tools. Note that this parameter defines the default maximum for all java bridges, however most memory intensive java bridges (e.g JDBC bridges) have the ability to define its own maximum memory in their last parameter called Miscellaneous.

Additional customizations (e.g. port numbers, Windows service names) of the MIMB Application Server can be performed in the following configuration file:
$MIMB_HOME/conf/tomcat/conf/tomcat.properties

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!