Creating WebSphere Business Monitor databases

You use WebSphere® Business Monitor Launchpad to create the WebSphere Business Monitor databases: State, Runtime, Historical, and Repository. The Launchpad creates the databases by running a set of database scripts.

These scripts contain the SQL statements needed to create the databases, configure them with configuration values, define the table spaces, and create the static database tables and indexes. The DB2® Cube Views™ must be installed before you can create the Historical database.

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.

When the State, Runtime, and Historical databases are created, the following information for each database is stored in the Repository database:
  • Database name.
  • Database schema
  • Database type
  • Host name on which the database was created
  • Operating system on which the database was created
The Repository database must be created before or at the same time the other databases are created.
Important: Before creating WebSphere Business Monitor databases, you must either remove or drop all databases that were previously created for a previous installation of WebSphere Business Monitor if you want to use the same databases names. Alternatively, you can specify databases names that are different from any previously created WebSphere Business Monitor databases.

To create one or more of the databases using the Launchpad, complete the following steps:

  1. On the Launchpad main window, click Create Databases.
  2. On the Create Databases window, select the check box next to each database you want to create, and then click Next. You can create four databases: State, Runtime, Historical, and Repository. Selecting the check box next to the Databases option selects all databases under it.
  3. On the Software Prerequisites window, the Launchpad displays the status of the database prerequisite. The status is:
    • Installed: Indicates that the database prerequisite is already installed.
    • Not Installed: Indicates that either the database prerequisite is not installed, or an unsupported version of the prerequisite is installed. If the database prerequisite (DB2) is not installed, click the prerequisite's name to expand the section, and then click Install to install it. The Launchpad then installs DB2 from the Software Prerequisites window. If an unsupported version of DB2 is already installed, a message displays asking you to exit the Launchpad and upgrade the software manually.
    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.
    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 the database prerequisites have been installed, click Start Database Creation to start the WebSphere Business Monitor installer. The Launchpad determines the status of the Repository database. There are three possibilities:
    1. If the Repository database exists on the current machine, the installation continues and the installer starts.
    2. If the Repository database does not exist, but you selected the Repository database on the Create Databases window, the installation continues and the installer starts.
    3. If the Repository database does not exist, and you did not select the Repository database on the Create Databases window, the following message displays:

      "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."

      You can do one of the following:

      1. If the Repository database is intended to exist on the current machine, click Cancel to stop the installation. Then click Back to return to the Create Databases window, and select the Repository database.
      2. 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 to display the Repository Database Information dialog where you enter the following information for the Repository database:
        • Database name
        • User ID of a valid user with DB2 administrative authority.
        • Password of the User ID
        • Password confirmation
        Enter the required information, and click OK to start the installer. If you click Cancel, the installation is terminated.
  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. 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, specify where to install the WebSphere Business Monitor components. 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. To create the State database, on the State Database Creation panel, enter the required information for creating the State database. The database name and database schema will be stored in the Repository database.Complete the following fields:
    1. In the Name field, type the database name.
    2. In the Schema field, type the database schema.
    3. In the User ID field, type the user ID of a user with DB2 administrative authority.
    4. In the Password field, type the password for the user ID.
    5. In the Backup directory field, type the path of the directory used for the database backup. Click Browse to select this directory.
      Important: The Backup Directory path and name must not contain any spaces. Otherwise, the backup will fail.
    6. In the Table Space Directory, type the path of the database Table Space directory. field. Click Browse to select this directory.
    7. Click Next to continue.
  8. To create the Runtime database, on the Runtime Database Creation panel, enter the required information for creating the Runtime database. The database name and database schema will be stored in the Repository database. Complete the following fields:
    1. In the Name field, type the database name.
    2. In the Schema field, type the database schema.
    3. In the User ID field, type the user ID of a user with DB2 administrative authority.
    4. In the Password field, type the password for the user ID.
    5. In the Backup directory field, type the path of the directory used for the database backup. Click Browse to select this directory.
      Important: The Backup Directory path and name must not contain any spaces. Otherwise, the backup will fail.
    6. In the Table Space Directory field, type the path of the database Table Space directory. Click Browse to select this directory.
    7. Click Next to continue.
  9. To create the Historical database, on the Historical Database Creation panel, enter the required information for creating the Historical database. The database name and database schema will be stored in the Repository database. Complete the following fields:
    1. In the Name field, type the database name.
    2. In the Schema field, type the database schema.
    3. In the User ID field, type the user ID of a user with DB2 administrative authority.
    4. In the Password field, type the password for the user ID.
    5. Click Next to continue.

  10. To create the Repository database, in the Repository Database Creation panel, enter the required information for creating the Repository database. The Repository database contains the information about the other databases (State, Runtime, and Historical). Complete the following fields:
    1. In the Name field, type the database name.
    2. Do not type anything in the Schema field. The database schema is already entered and cannot be changed.
    3. In the User ID field, type the user ID of a user with DB2 administrative authority.
    4. In the Password field, type the password for the user ID.
    5. Click Next to continue.
  11. A summary of your selections is displayed on the Summary panel. It includes information for the destination directory, a listing of selected features and components, and the total amount of disk space to be used for the installation. Click Next to start installing the selected features and components.

    The wizard checks the disk space to verify that there is sufficient space for installing the selected features. 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 creation of the databases.

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

Copyright IBM Corporation 2005, 2006. All Rights Reserved.