Installing the Dashboard Client component

You use the Launchpad to install the Dashboard Client component.

The WebSphere® Business Monitor installation process installs the Dashboard Client component without creating the required dashboard and views. You need to create these views in the WebSphere Portal after you finish the installation.

Refer to Administering dashboards and views for the detailed steps of creating the dashboard and adding the different views.

Important: The Dashboard Client component can only be installed onto a machine that does not contain the prerequisites. The Dashboard Client component and its prerequisites must be installed using only the Launchpad onto a machine that has no previous installation of the prerequisites. Do not configure any of the prerequisites before installing the Dashboard Client component.

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

Before the Dashboard Client component can be installed, the following databases must already be created:
  • Repository
  • Runtime
  • Historical

To install the Dashboard Client component using the Launchpad, complete the following steps:

  1. On the Launchpad main window, click Install Product.
  2. On the Select Features window, select the Dashboard Client component, and then click Next. The Software Prerequisites window is displayed.
  3. On the Software Prerequisites window, all prerequisites of the Dashboard Client 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 of this component.
    Important: In order to avoid errors during the WebSphere Portal PTF installation, you must ensure that prior to installing DB2 Universal Database™, the host short name is limited to eight characters. If you need to change the host short name, you must change it, reboot the machine, and then install the DB2®. If you must use a longer host name, refer to the topic named Installing Dashboard Client with a long host name for details on how to solve this problem.
    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 determines the status of the databases required by the selected features. There are several possibilities:
    1. If all the databases exist on the current machine, the installation continues, and the installer starts.
    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 administrative privileges
      • Password of the User ID
      • Password confirmation
      Enter the required information, and click OK to start the installer. If you click Cancel on the Repository Database Information 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 about the other databases, the Launchpad reads the information from the Repository database, and the installer starts. If the Runtime and Historical 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 about 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 about 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 WebSphere Business Monitor 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 Dashboard Client. 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 Portal Information panel, enter the required information about the WebSphere Portal Server on which the Dashboard Client component will be installed.
    1. In the Profile name field, type the profile name that contains the specified cell, or click Browse to select a profile. (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 cell name 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 node name 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 application server name on which the WebSphere Portal is installed. (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 Portal User ID field, type the user ID of a valid user.
    6. In the Password field, type the password for the user ID.
    7. In the Configuration Hostname field, type the host name on which the WebSphere Portal application server was created.
    8. In the Configuration Port field, type the port number used to access the WebSphere Portal configuration utility.
    9. In the Process Server (BPEL) hostname field, type the host name of the machine on which WebSphere Process Server 6.0.1 is installed.
    10. In the Process Server (BPEL) bootstrap port field, type the bootstrap port on the WebSphere Process Server (BPEL) machine.
    11. Click Next to continue.
  8. On the DB2 Alphablox Configuration panel, enter the following information about the DB2 Alphablox:
    1. In the Installation Directory field, type the name of the DB2 Alphablox installation directory, or click Browse to select the directory. (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.)
    2. In the User ID, type the user ID of a valid user of DB2 Alphablox. (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.)
    3. In the Password field, type the password of the user ID. (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.)
    4. In the Hostname field, type the host name on which the DB2 Alphablox is installed. (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 Telnet Port field, type the port number used to access the DB2 Alphablox Telnet utility. (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.)
    6. To set the WebSphere Business Monitor theme as the default theme for the AlphaBlox, select the Set WebSphere Business Monitor as the DB2 Alphablox default theme check box.
    7. To set the WebSphere Business Monitor theme as the default theme for the WebSphere Portal, select the Set WebSphere Business Monitor as the WebSphere Portal default theme check box.
    8. To use the WebSphere Business Monitor welcome page instead of the default WebSphere Portal welcome page when you log in to WebSphere Portal, select the Use WebSphere Business Monitor welcome page for WebSphere Portal check box.
    9. Click Next to continue.
  9. 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 Dashboard Client component.

    The wizard checks the disk space to verify that there is sufficient space for installing the Dashboard Client 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 Dashboard Client.

  10. When the installation is completed, on the Finish panel, click Finish to exit the installer.
Note: The WebSphere Portal will be in a stopped state upon the completion of the Dashboard Client installation. In case it remains started, make sure that you stop and start the WebSphere Portal again prior to attempting to view any installed Dashboard portal pages.
Related concepts
WebSphere Business Monitor prerequisites
Related tasks
Creating WebSphere Business Monitor databases
Installing the Monitor Server component
WebSphere Business Monitor Launchpad
Running the Launchpad
Administering dashboards and views

Copyright IBM Corporation 2005. All Rights Reserved.