Starting Wizard

The Monitor Server component can be deployed automatically on WebSphere Application Server using the BI Monitor Installation Wizard by selecting the Automatic Deployment as the deployment type.

The wizard will lead you through a set of steps to gather the required information for the Monitor Server deployment, and then the wizard will deploy the Monitor Server automatically.

When you are deploying the Monitor using the Deployment Manager to a node that exists in a remote machine other than the Deployment Manager machine, then the following fields must be entered with the values of the remote node environment:

In case of network deployment, you must disable the wizard validation that checks and validates the above items. This is done by editing the runwizard.sh or the runwizard.bat by which you run the installation wizard and adding the following switch -Dmonitor.wizard.validators=false to the Run command as follows:

In the runwizard.bat:

"%WAS_HOME%\java\bin\java" "%CLIENTSAS%" -Dmonitor.wizard.validators=false  "-Dwas.install.root=%WAS_HOME%" "-Dwas.repository.root=%CONFIG_ROOT%" -Dcom.ibm.CORBA.BootstrapHost=%COMPUTERNAME% -cp "%WAS_HOME%\classes";"%WAS_HOME%\lib\xerces.jar";"%WAS_HOME%\l ib\j2ee.jar";"%WAS_HOME%\lib\admin.jar";"%WAS_HOME%\lib\wsexception.j ar";"%WAS_HOME%\lib\wasjmx.jar";"%WAS_HOME%\lib\management.jar";"% WAS_HOME%\lib\sas.jar";"%WAS_HOME%\lib\utils.jar";"%WAS_HOME%\lib\ wssec.jar";"%WAS_HOME%\lib\ras.jar";"%WAS_HOME%\lib\bootstrap.jar";"% WAS_HOME%\lib\emf.jar";"%WAS_HOME%\lib\ffdc.jar";"%WAS_HOME%\lib\s oap.jar";"%WAS_HOME%\lib\classloader.jar";"%WAS_HOME%\lib\wasproduct .jar";WBIMonitor424-FixPack4.jar -Djava.ext.dirs="%WAS_HOME%\java\jre\lib\ext";"%WAS_EXT_DIRS%" run

In the runwizard.sh:

${WAS_HOME}/java/bin/java "${CLIENTSAS}" -Dmonitor.wizard.validators=false "-Dwas.install.root=${WAS_HOME}" "-Dwas.repository.root=${CONFIG_ROOT}" -Dcom.ibm.CORBA.BootstrapHost=${COMPUTERNAME} -cp ${WAS_HOME}/ classes:${WAS_HOME}/lib/xerces.jar:${WAS_HOME}/lib/ j2ee.jar:${WAS_HOME}/lib/admin.jar:${WAS_HOME}/lib/ wsexception.jar:${WAS_HOME}/lib/wasjmx.jar:${WAS_HOME}/lib/ management.jar:${WAS_HOME}/lib/sas.jar:${WAS_HOME}/lib/ utils.jar:${WAS_HOME}/lib/wssec.jar:${WAS_HOME}/lib/ ras.jar:${WAS_HOME}/lib/bootstrap.jar:${WAS_HOME}/lib/ emf.jar:${WAS_HOME}/lib/ffdc.jar:${WAS_HOME}/lib/soap.jar:${WAS_HOME}/ lib/classloader.jar:${WAS_HOME}/lib/wasproduct.jar:WBIMonitor424-FixPack4.jar -Djava.ext.dirs=${WAS_HOME}/java/jre/lib/ ext:${WAS_EXT_DIRS} run

In case you choose to install and deploy the BI Monitor on a Network deployment environment, then the Deployment Manager must be started and run at installation time.

You must un-deploy Monitor Sever that exists on WAS, in case there is a previous one.

The following are the wizard steps for installing and deploying Monitor Server:

The BI Monitor Installation Wizard starts on the Welcome screen. For all wizard steps, to go forward to the next step, click Next. To go back to the previous step click Back. You can exit the wizard at any time by clicking Cancel.

  1. In the next screen you should enter the Monitor installation directory (<Monitor>) where the necessary folders and files will be extracted. This directory also will be the BI Monitor Working Directory. You can accept the default path or change this path to a new folder. Then, you can click Next to continue.

Monitor Installation Directory page

  1. In the next screen read the displayed instructions, and then click Next.

Installation Instructions page

  1. The next screen is the Deployment Type where you can select one of the following deployment types:

Deployment Types page

Select the Automatic Deployment option and then click Next to continue.

  1. The next screen of the BI Monitor Installation Wizard appears if you select the Automatic Deployment option as the deployment type. In this screen, you should select one or more of the BI Monitor components to be installed. Select the Monitor Server option to install and deploy the Monitor Server component and then click Next to continue.

Selecting Automatic Deployment Option page

  1. In the next wizard screen you will be asked to enter the path and the type of the Database JDBC driver file. For IBM DB2 database, this driver file is named db2java.zip and is located in the <DB2>\Java folder. For Oracle database, this driver file is named classes12.zip and is located in the <Oracle>\jdbc\lib folder. Enter the required path or click Browse to select the path. Then select the driver type from DB Driver Type combo box. If the entered path is not correct, then you will be informed by a message, and the wizard will not continue until you enter the correct path. Then, you can click Next to continue.

Enter Path and Type of the Database JDBC Driver File page

  1. In the next screen you will be asked to enter the following information for the Monitor database:

Where <Oracle_Server_Name> is the name or the IP address of the Oracle Database Server machine, and <Oracle_Server_Port_Number> is the Oracle Server Port Number (the default port is 1521)

The wizard will check the connection with the database using the entered database name (or URL), user name and password. If one or more of the entered parameters are not correct, then you will be informed by a message, and the wizard will not continue until you enter the correct parameters. Then click Next to continue.

Checking Connection with Database Using Entered Database Name (or URL),
User Name and Password

The wizard will also check this database to verify if it is a newly created database or a database of an earlier version of the BI Monitor that requires to be upgraded to the recent version's modifications. If the specified database belongs to the previous version of BI Monitor, then a message will appear to tell you that the specified database belongs to a previous version of BI Monitor, and it needs to be upgraded using the Database Migration Utility before starting this Installation Wizard. Then the wizard will be terminated.

Please refer to the section entitled BI Monitor Database Migration in Chapter 6: Upgrading your Existing Version of BI Monitor to the Recent Version in this guide for detailed information about the Database upgrade.

  1. In the next step you should specify the names of the required TableSpaces for each group of tables and indexes in the Monitor database as follows:

If you leave this field empty, then the database default TableSpace will be considered and used as the default TableSpace.

You can specify a different TableSpace name for each group of tables or indexes. Alternatively, you can specify the same TableSpace for more than one group of tables or indexes. In the later case these groups of tables and/or indexes will use the same TableSpace for storing the data physically on the hard drive.

If you leave a blank field without specifying a TableSpace name, then the default TableSpace will be used for the corresponding group of tables or indexes.

The specified TableSpace should have been previously created in the Database server. Otherwise, the deployment will not be performed properly and you will not be able to create the database tables.

In case you have an existing database that belongs to a previous version and contains data, then you will only be able to enter the default TableSpace. All other fields that can hold the multiple TableSpaces Names will be disabled.

Click Next to continue.

Specifying Names of the Required TableSpaces page

  1. In the next screen you will be asked to select the workflow engine(s) that the BI Monitor will monitor their run-time data. There are two workflow engines that can be selected:

Selecting Workflow Engine(s) page

You can select one of these options or you can select a combination of them. According to your selection, the wizard steps will vary to let you enter the required information for the selected option as will be described in the following sections.

If the specified BI Monitor database belongs to a previous version of BI Monitor, then the MQWF option will be selected by default and its check box will be disabled so that you cannot de-select it.