Skip to main content

Application Server Execution and Initialization

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

  • Windows
  • On Windows, you must "Run as administrator" the %MM_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 $MM_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).

The final initialization steps of the setup are performed over the web browser as follows:

  1. Connection
    Connecting to the server on Windows can be simply achieved by opening the Metadata Management link in the home directory. In all cases, you can connect to the server using your internet browser to open by default: http://localhost:11480/MM. Note that the default port of this URL number may have been changed by the Setup utility in the section Server Installation and Configuration.
  2. Database
    Define the connection to the previously created database (in the above steps), by providing the database type, user, password, and URL (JDBC connection). If you are using the PostgreSQL database bundled with the software package for Windows, then all these parameters should be already preset. Press the Test Connection button to verify proper database connectivity. Finally, when pressing the Save button, the Application Server will create all the necessary tables in the database.
  3. License
    Click on the Download License Information link to obtain the obtained your HostInfo.xml file that should be sent with your license request. Warning: Make sure you are NOT connected to any VPN during that step, then your license will work independently of your VPN connection. After you have received your MM.lic license file, browse for it and click on the Save Licensebutton. Alternatively, the host info file can be generated at the Windows command line using $MM_HOME/bin/HostFileGen.sh, or HostFileGen.bat on Windows. This will generate your HostInfo.xml file (in the bin directory) that should be sent with your license request. After you have received your MM.lic license file, copy it to $MM_HOME/conf/MM.lic and restart the application server.
  4. Login
    Login as "Administrator" with password "Administrator". Note that you should change that password later in the application by going to: MANAGE > Users.

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 – let us know how we can improve!