Deploying the management server WAR file on WebSphere Application Server v7.0

You can use IBM® Installation Manager to install the management server and its associated databases and data files to an application server computer. However, installation is not complete until you deploy the management server Web archive (WAR) file to the application server. Use this task to deploy the management server WAR file on WebSphere® Application Server.

Before you begin, install WebSphere Application Server. To avoid path length issues, avoid installing WebSphere Application Server into a long path. For example, if you install WebSphere Application Server to a Windows computer, C:\WAS70 is an acceptable installation location.

After you install WebSphere Application Server, start the instance of the Apache Derby database that is installed with WebSphere Application Server. To start the Derby database, complete the following, where was_folder is the folder in which WebSphere Application Server is installed.
  • Windows: Run the was_folder\derby\bin\networkServer\startNetworkServer.bat batch file.
  • AIX®/Linux/Solaris: Run the was_folder/derby/bin/networkServer/startNetworkServer script.

Use the Integrated Solutions Console of WebSphere Application Server to deploy the WAR file. The default location of the administrative console is http://hostname:9043/ibm/console, where hostname is the host name of the computer on which WebSphere Application Server is installed.

To deploy the management server WAR file using the Integrated Solutions Console of WebSphere Application Server:

  1. Click Resources > JDBC > Data Sources and create a data source with the following properties. Use the defaults for all other properties:
    Step 1: Enter basic data source information
    • Data source name: OptimServerDS
    • JNDI name: jdbc/OptimServerDS
    Step 2: Select JDBC provider
    Select an existing JDBC provider: Derby Network Server Using Derby Client 40 (XA)
    Step 3: Enter database specific properties for the data source
    Database name: OptimServerDB;create=true
    When you are done, click Save to save the data source, and then click Test connection to test the data source.
  2. Click Applications > New Application > New Enterprise Application and deploy the WAR file with the following properties. Use the defaults for all other properties:
    Preparing for the application installation
    The management server WAR file is shared_installation_directory/server/app/management-server.war, where shared_installation_directory is the installation directory that you specified for the IBM Optim Shared package group. For example, the default location for the management server WAR file on Microsoft Windows is C:\Program Files\IBM Optim\shared\server\app\management-server.war. If you prefer, you can click Browse to browse for the file. Use Fast Path to install the application.
    Step 3: Map resource references to resources
    Click Browse, select OptimServerDS and click Apply.
    Step 5: Map context roots for Web modules
    Context Root: /server
    The WAR file can take several minutes to deploy. When you are done, click Save to save the configuration.
  3. Click Applications > Application types > WebSphere enterprise applications > management-server_war > Class loading and update detection, select Classes loaded with local class loader first (parent last), click Apply, and click Save.
  4. Click Servers > Server types > WebSphere application servers > server1 > Java and Process Management > Process definition > Java Virtual Machine > Custom properties, and add the following properties.
    com.ibm.optim.host.name
    The name of the host on which you have installed WebSphere Application Server.
    com.ibm.optim.host.port
    The port on which the web container is running. The default port is 9080.
    com.ibm.optim.registry.url
    The location of the registry. This is http://hostname:port/server/registry, where hostname is the value of com.ibm.optim.host.name, and port is the value of com.ibm.optim.host.port.
    com.ibm.optim.repository.url
    The location of the repository. This is http://hostname:port/server/repository, where hostname is the value of com.ibm.optim.host.name, and port is the value of com.ibm.optim.host.port.
    When you are done, click Save to save the configuration.
  5. Stop and restart WebSphere Application Server.
  6. Click Applications > Application types > WebSphere enterprise applications and verify that management-server_war is running. If not, select the Select box for management-server_war and click Start. The application can take several minutes to start.
After you deploy the management server on WebSphere Application Server, you must configure the proxies to access the registry and repository on the management server.