Continuing the Wizard Steps

Now after entering the required information for either the MQWF or WMQI option, the wizard steps will continue to complete installing the Monitor Server component.

  1. In the next screen, you will be asked to enter the Installed version of IBM WebSphere Application Server and its installation path.

Enter the required path or click Browse to select the path. 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.

  1. In the next screen, you will be informed with the Monitor Server installation summary. The wizard now is ready to start extracting the necessary folders and files needed for installing the BI Monitor Server Component and then update the Monitor Enterprise Archive file (monitor.ear) with the new parameters that you have specified in the wizard steps.  Click Next to continue.

  1. After extracting the necessary folders and files needed for BI Monitor Server deployment, the wizard now is ready to do the following:

You have the option to do either of the following:

The created deployment script will be placed in <Monitor>\install directory. To deploy the Monitor by using this script, run the batch file named monitorInstall.bat in Windows platform (or the file named monitorInstall.sh in the AIX or Solaris platforms) in the previous path. Now click Next to continue.

Important:

In order to deploy the BI Monitor automatically, the automatic deployment wizard must connect to WebSphere Application Server using the SOAP port. The SOAP port should have the default value which is 8880.

If you are using IBM WebSphere Network Deployment or if two or more installations of WebSphere Application Server exist on the same machine on which you will install the BI Monitor, then the SOAP port number may have different value other than this default value.

In this case you will get a message that says "WASX7023E: Error creating "SOAP" connection to host "localhost"; exception information: com.ibm.websphere.management.exception.ConnectorNotAvailableException WASX7213I: This scripting client is not connected to a server process; please refer to the log file <WebSphere>\logs\wsadmin.traceout for additional information." when the wizard starts the deployment if you select the Deploy check box. However, the deployment will not start. You should then un-check the Deploy check box in the wizard, and then do the following:

if "%WAS_Version%"=="was_5.0" call %WAS_HOME%\bin\wsadmin.bat -conntype SOAP -port <Port_Value> -f was5\InstallMonitor.tcl

if "%WAS_Version%"=="was_5.0" call %WAS_HOME%\bin\wsadmin.bat -conntype SOAP -port <Port_Value> -f was5\UninstallMonitor.tcl

${WAS_HOME}/bin/wsadmin.sh -conntype SOAP -port <Port_Value> -f was5/InstallMonitor.tcl;

${WAS_HOME}/bin/wsadmin.sh -conntype SOAP -port <Port_Value> -f was5/UninstallMonitor.tcl;

  1. Now the BI Monitor Server installation has finished. You will need to start the deployed Application Server from the WebSphere Administrator's Console, in order to run BI Monitor. Click Finish to exit this installation wizard.