Starting the manager on an application server

To run and manage services that are located in a registry, you must first start the manager on its application server. After the manager is started on the application server, you can access the manager at any time.

Before you can start the manager, you must install the manager. You must also perform initial configuration of the manager and the components that the manager uses to run services. For example, you must deploy the manager WAR file to the application server.

To start the manager on an application server:

  1. Start the application server. If the application server is set to start the manager web application automatically, then the manager is started immediately after the application server. If you deployed the manager to the version of WebSphere® Application Server Community Edition that is delivered with the manager, then complete the following step. In this step, shared_installation_directory is the installation directory that you specified for the manager.
    • Microsoft Windows computers: Click Start > All Programs > IBM Optim > Start WAS-CE, or run the script shared_installation_directory\WebSphere\AppServerCommunityEdition\bin\startup.bat.
    • Linux or UNIX computers: Run the script shared_installation_directory/WebSphere/AppServerCommunityEdition/bin/startup.sh.
  2. If necessary, start the manager web application by using the application server console. If you deployed the manager to the version of WebSphere Application Server Community Edition that is delivered with the manager, then complete the following steps:
    1. Use a web browser to access and sign into the Administrative Console. The default location is at http://hostname:port/console/, where hostname is the host name or IP address of the WebSphere Application Server Community Edition computer and port is the port number. The default port number is 8080. Use user ID system and password manager to access the Administrative Console.
    2. Click Web App WARs.
    3. Click Start for the component with an URL of /optim.
To automate the starting of the manager after you restart the computer, configure the application server as a Windows service or Linux or UNIX daemon.