Installing the Monitor Server component

You use the Launchpad to install the Monitor Server component.

Before the Monitor Server component can be installed, the following databases must already be created:
  • Repository
  • State
  • Runtime

During installation, using the Launchpad, you can go to the Progress panel at any time to check the status of the installation. All buttons except the Cancel button are disabled when this panel is displayed.

Important: The Monitor Server must be installed on a standalone node.

To install the Monitor Server component using the Launchpad, complete the following steps:

  1. On the Launchpad main window, click Install Product.
  2. On the Select Features window, select Monitor Server to install the Monitor Server component including the Adaptive Action Manager, Schema Generator and the WebSphere® Business Monitor Administrative Console extensions. The extensions, which are extensions to the WebSphere Application Server administrative console, are used for administering Monitor Server, Adaptive Action Manager, and Schema Generator. If the component has already been installed on the system, the component is selected and its check box is disabled.

    After selecting the component to install, click Next. The Software Prerequisites window is displayed.

  3. On the Software Prerequisites window, all prerequisites of the Monitor Server component are displayed with their installation status. The status is one of the following:
    • Installed: Indicates that the software prerequisite is already installed.
    • Not Installed: Indicates that either the software prerequisite is not installed, or an unsupported version of the prerequisite is installed. If the software prerequisite is not installed, click the prerequisite's name to expand the section, and then click Install to install it. If an unsupported version of the software prerequisite is already installed, a message displays asking you to exit the Launchpad and upgrade the software manually.
    Refer to the Software Prerequisites section in the Installation Readme for details about the prerequisites for this component.
    Important: After installing DB2® using the WebSphere Business Monitor Launchpad, you must you must do the following:
    • On Windows® platforms: Close the Launchpad and all command windows or Explorer windows. Make sure that DB2 is started before you attempt to install any feature. You can start DB2 by typing the "db2start" command. Then you can restart the Launchpad and proceed with the remainder of the installation.
    • On the AIX® platform: Do the following:
      1. Exit the Launchpad.
      2. Create /.profile and add this line:. /home/db2inst1/sqllib/db2profile (Note that there is a space between the period and the first slash).
      3. Uncomment the last line from the /.dtprofile
      4. Log out.
      5. Log back in.
      6. Start DB2 by typing the "db2start" command
      7. Restart the Launchpad and proceed with the remainder of the installation.
  4. After all prerequisites have been installed, click Start Monitor Installation to start the WebSphere Business Monitor installer. The Launchpad will determine the status of the databases required by the selected features. There are several possibilities:
    1. If all databases exist on the current machine, the installation will continue, and the installer will start.
    2. If the Repository database does not exist on the current machine, the following message is displayed:

      "The Repository database information is not available in the CommonInstallParam.tcl file. If the Repository database exists on a remote machine, make sure the database is cataloged on this machine, and then click OK to enter the database information. If the Repository database is planned to be on this machine, click Cancel to stop the current install, and then use the Launchpad to create the Repository database."

      If the Repository database has been created on a remote machine, make sure that the database is cataloged on the current machine. You must use DB2 commands or the DB2 Control Center to catalog the database. Then click OK on the message to display the Repository Database Information dialog where you can enter the following information for the Repository database:
      • Database name.
      • User ID of a valid user who has database administrative privileges.
      • Password of the valid User ID.
      • Password confirmation.
      Enter the required information, and click OK to start the installer. If you click Cancel on the Repository Database Information panel or in the message, the installation is terminated.
    3. If the Repository database exists or is cataloged on the current machine, and it contains the information of other databases, the Launchpad reads the information from the Repository database, and starts the installer. If the State and Runtime databases have been created on a remote machine, make sure that the databases are cataloged on the current machine. You must use DB2 commands or the DB2 Control Center to catalog the databases. The name used to catalog each database must match the name of the corresponding database on the remote machine.
    4. If the Repository database exists or is cataloged on the current machine, but it does not contain the information of the other databases (the other databases have not been created), a message is displayed for each missing database. The message informs you that the information for the database does not exist either in the Repository database or in the commonInstallParam.tcl, and you must create the databases before you can install the selected features. On the message, click OK to cancel the installation. Go to Creating WebSphere Business Monitor databases to create the missing databases.
  5. When the installer starts, the Software License Agreement panel appears. Read the License Agreement carefully, and select "I accept both the IBM and the non-IBM terms" to accept the agreement. Then click Next to continue. If you select "I do not accept the terms in the License Agreement" and click Next, a message appears asking you to confirm your selection. Clicking Yes exits you from the installation. Clicking No returns you to the Software License Agreement panel.
  6. On the Destination panel, you specify where to install the components. The Destination panel will not appear if you have defined the WebSphere Business Monitor databases on the same machine on which you are installing the Monitor server. The default directory path and name is C:\IBM\WebSphere\Monitor on the Windows platform and /opt/IBM/WebSphere/Monitor on the AIX platform. You can accept the default path or change this path to a new directory by clicking Browse and selecting the other directory. Click Next to continue.
  7. On the WebSphere Application Server Configuration panel, you enter the configuration of the current WebSphere Application Server installation:
    1. In the Profile name field, type the profile name that contains the specified cell. (This field will be filled in by default with the information passed to the installer by the Launchpad. You can change this value if needed, but try not to exceed 8 characters.)
    2. In the Cell name field, type the name of the cell that contains the specified node. (This field will be filled in by default with the information passed to the installer by the Launchpad. You can change this value if needed, but try not to exceed 18 characters.)
    3. In the Node Name field, type the name of the node on which the specified application server exists. (This field will be filled in by default with the information passed to the installer by the Launchpad. You can change this value if needed, but try not to exceed 8 characters.)
    4. In the Server name field, type the name of the application server on which you want to install the selected component or components. (This field will be filled in by default with the information passed to the installer by the Launchpad. You can change this value if needed.)
    5. In the Generation Directory field, type the name of the generation directory that will be used when the WebSphere Business Monitor Administrative Console is used to import business measures models.
    6. Click Next to continue.
  8. If the Monitor Server is being installed on a system where WebSphere Application Server security is enabled, an additional panel named WebSphere Application Server Security Configuration is displayed. On this panel, complete the following fields:
    1. In the User ID field, type a user ID of a valid user who has the authority to start and stop the WebSphere Application Server. The user id is defined when you enable the WebSphere Application Server security through the WebSphere Application Server administrative console.
    2. In the Password field type the password of the entered user ID
    3. In the Confirm Password field, type the password again to confirm it.
    4. Click Next to continue.
    Note: If you are planning to enable WebSphere Application Server global security after installing the Monitor Server, you must update the authentication alias with a valid User ID and password before you enable global security.

    Refer to the topic named Changing User ID and password for the created authentication alias for the detailed steps on how to perform this task.

  9. On the Action Catalog database panel, enter the database information for the Adaptive Action Manager database, which is known as the Action Catalog. The Action Catalog database will be created during the Monitor Server installation on the local machine. Complete the following fields:
    1. In the Name field, type the Action Catalog database name.
    2. In the Host Name field, type the host name or IP address of the Action Catalog database. The value for this field should be the local host name or IP address as the Action Catalog database will be created on the local machine.
    3. In the Port Number field, type the Action Catalog database port number.
    4. In the User ID field, type the User ID of a valid user with DB2 administrative authority.
    5. In the Password field, type the password for the user ID.
    6. Click Next to continue.
  10. A summary of your selections is displayed on the Summary panel. It includes information for the destination directory, a listing of selected components, and the total amount of disk space that will be used for the installation. Click Next to start installing the Monitor Server component.

    The wizard checks the disk space to verify that there is sufficient space for installing the Monitor Server component. A warning message informs you if there is not enough disk space in the selected drive. The Next button is disabled. Click Back to return to the Summary panel. Free enough space on the specified drive, then click Next again to start installing the selected components. If you cannot free enough space, you can change the destination directory by revisiting the Destination panel. If there is enough disk space, the Progress panel is displayed showing the installation progress. Only the Cancel button is enabled while the this panel is displayed. The Cancel button is used to abort the installation of the Monitor server.

  11. When you have completed the installation, on the Finish panel, click Finish to exit the installer.
Related concepts
WebSphere Business Monitor prerequisites
Related tasks
Creating WebSphere Business Monitor databases
Installing the Dashboard Client component
WebSphere Business Monitor Launchpad
Running the Launchpad

Copyright IBM Corporation 2005, 2006. All Rights Reserved.