===============================================================================
Installing IBM® WebSphere® Business Integration (WBI) Monitor™ v4.2.3 Fix Pack 2b7
===============================================================================

The contents of this file describe how to run the IBM WBI Monitor  4.2.3 Fix Pack2b7 Installation Wizard.

The WBI Monitor 4.2.3 Fix Pack 2b7 Installation Wizard starts by running the jar file named mon423fp2b7.jar from the location where you have extracted the contents of the zip file that you downloaded from the Internet.

Before starting the WBI Monitor 4.2.3 Fix Pack 2b7 Installation Wizard, you have to do the following:

  1. Make sure that a previous installation of the full version of the WBI Monitor v4.2.3 (installed by running the mon423.jar) already exists (with or without Fix Pack1), and has not been uninstalled.  Otherwise, the installation of this fix pack will not be performed successfully.  For more information about installing the full version of WBI Monitor 4.2.3, please refer to the install.txt file that is shipped with that release.

  2. It is strongly recommended that you make a copy of the following file, which has values in your previous deployment of WBI Monitor v4.2.3, as you may need it:

  3. Stop Monitor Service and then stop Monitor Server as all.

  4. Stop the MQWorkflow server. You must do this, otherwise it might be very harmful for the upgrade operation and even for MQWorkflow itself.

  5. You should completely un-deploy the existing WBI Monitor before you start deploying the new WBI Monitor application that belongs to this fix pack.

  6. After deploying the Fix Pack on WebSphere, you have to delete the directory named MonitorServer which is located in <WAS_HOME>/temp/<WAS_NODE_NAME>/, then restart the application server.

Where:

  1. Backup both of Monitor Database and MQWorkflow database.

  2. Perform the database migration if you have an existing database of  Monitor 4.2.3 FP1 that already contains data to adhere to the latest modification in the Monitor 4.2.3 Fix Pack2b7, and to migrate the stored data to the upgraded database. The database migration can be done as in the following:

    1. Connect to MQWorkflow database as the owner of the MQWorkflow tables and run the migrateEventQueue.sql file.

    2. Connect to WBI Monitor database as the owner of the WBI Monitor tables and run the migrateMonitor.sql file.

    3. The following are the database privileges necessary to run both files migrateEventQueue.sql and migrateMonitor.sql respectively:

        For Monitor database:

    • CREATE INDEX

    • ALTER TABLE

    For MQ Workflow Database:

    • CREATE SEQUENCE

    • DROP SEQUENCE

    • CREATE INDEX

    • DROP INDEX

    • CREATE TRIGGER

    • DROP TRIGGER

    • ALTER TABLE

    • UPDATE TABLE

    • CREATE PROCEDURE

    • EXECUTE PROCEDURE

    • DROP PROCEDURE

    1. If any error occurs: restore the databases, contact the WBI Monitor Support for troubleshooting and report the error.

  1. Make sure that the IBM jdk 1.3.0 is installed on your machine. Alternatively, you can use the IBM JDK that is shipped with IBM WebSphere Application Server.

  2. Install the new version of WBI Monitor v4.2.3 Fix Pack2b7 and deploy the new application on WebSphere Application Server. You must install the Fix Pack file mon423fp2b7.jar on the same installation (Home) directory where the full version has been installed.

To start the WBI Monitor 4.2.3 Fix Pack 2 Installation Wizard, run the mon423fp2b7.jar  file by performing the following steps:

On Windows platform:

  1. Start a command prompt window.

  2. Make sure that the full path of the java.exe is included in the Path environment variable. Otherwise, you should change the directory to the location where the java.exe exists. For example, if you are using the IBM JDK that is shipped with IBM WebSphere Application Server, type the following, and then press Enter:

    CD C:\WebSphere\AppServer\java\bin\

Where C:\WebSphere\AppServer\ is the IBM WebSphere Application Server's installation path.

  1. Type the following in the command prompt, and then press Enter:

        java.exe -jar C:\temp\mon423fp2b7.jar

    Where C:\temp is the location where the mon423fp2b7.jar  file exists.

On AIX® and Solaris platforms:

  1. Start a terminal console as root.

  2. Make sure that the full path of the java is included in the PATH environment variable. Otherwise, you should change the directory to the location where the java exists. For example, if you are using the IBM JDK that is shipped with IBM WebSphere Application Server, type the following, and then press Enter:

                cd /usr/WebSphere/AppServer/java/bin/

            Where /usr/WebSphere/AppServer/ is the IBM WebSphere Application Server's installation path.

     

                cd /opt/WebSphere/AppServer/java/bin/

            Where /opt/WebSphere/AppServer/ is the IBM WebSphere Application Server's installation path.

     

  3. Type the following in the command prompt, and then press Enter:

java -jar /tmp/mon423fp2b7.jar 

Where /tmp is the location where the mon423fp2b7.jar  file exists.