Application Server Execution

The MIMB Application Server can be started manually or automatically as follows:

• Windows
  • On Windows, you must "Run as administrator" the %MIMB_HOME%\RestartApplicationServer.bat utility.
  • On Windows operating systems, you can alternatively use the Windows Services to control the Application Server by using the %MM_HOME%\RestartApplicationService.bat utility instead. This utility will create the Windows Service for the Application Server, if it was not already created by previous execution of this utility or the Setup.bat utility. At this point, you can simply use Windows Services to start, stop or restart the Application Server automatically.
    ‎When running the Application Server as a Windows Service, it is important to configure the user running such service to have full access rights to the needed files and applications. For example, the MIMB bridges involved in the metadata harvesting may need to invoke the SDK of third-party software such as the COM based API of CA ERwin, or SAP BusinessObjects Universe Designer.
    ‎In order to set such access rights, go to the services manager of Windows, right-click on the Application Server service. Then, go to the "Log On" tab to define an account by name under which the service will run.
• Linux
  • On Linux, you must "sudo" (as root) to execute the $MIMB_HOME/RestartApplicationServer.sh utility.
  • On Linux, administrators can use the system daemon directories (e.g. /etc/init.d/ or /etc/systemd/) to control the Application Server (either using the RestartApplicationServer.sh utility or directly controlling the tomcat server in the home directory).