Upgrading your Existing Version of BI Monitor to the Recent Version

This chapter contains the required information about upgrading your existing version of WebSphere BI Monitor (WBI Monitor v4.2.4 Fix Pack 3) to the recent version (WebSphere BI Monitor V4.2.4 Fix pack 4). This includes replacing the deployed version of BI Monitor application on WebSphere Application Server with the new version, as well as upgrading the existing Monitor database that already contains data stored in its tables to adhere to the latest modification in the recent version of BI Monitor database, and migrate the stored data to the upgraded database.

The BI Monitor upgrade must be performed in the following sequence:

  1. Un-deploy the existing version of BI Monitor Server completely from the WebSphere Application Server. On Windows, AIX and Solaris platform, you can perform the un-deployment either automatically or manually. On z/OS and OS/390 platforms you can only perform the un-deployment manually.

Refer to the section entitled BI Monitor Server Un-Deployment in Part 2 - Chapter 4: BI Monitor Installation of this guide for the detailed steps of automatic un-deployment of BI Monitor Server. Refer also to the section with the same title in Appendix A, Appendix B, and Appendix C in Part 2 of this guide for the detailed steps of the manual un-deployment of BI Monitor Server. Refer to the section entitled BI Monitor Deployment on OS/390 and z/OS Platforms in Part 3 of this guide for the un-deployment steps.

  1. Backup your existing Monitor database.

  2. Perform the Database Migration and Upgrade after completely un-deploying the existing version of the Monitor Server, in order to upgrade the existing database and its data to this version. The existing database must be of the previous version of the BI Monitor. If the existing database belongs to an earlier version before the stated version, then the upgrade must be done incrementally step by step from each version to its next version.

To perform the database upgrade, run the appropriate SQL file that exists in the migration\SQL folder as the following:

Before running these files, you should edit them in order to change the variable named $SCHEMA$ with the actual name of the tables schema  in each occurrence in the files.

  1. Install the new version of BI Monitor and Deploy the BI Monitor Server that belongs to the new version of BI Monitor after completing the upgrade and migration of the database.

Refer to the section entitled BI Monitor Server Installation and deployment in Part 2 - Chapter 4: BI Monitor Installation of this guide for the detailed steps of automatic deployment of BI Monitor Server. Refer also to Appendix A, Appendix B, and Appendix C in Part 2 of this guide for the detailed steps of the manual deployment of BI Monitor Server. Please refer to the section entitled BI Monitor Deployment on OS/390 and z/OS Platforms in Part 3 of this guide for the deployment steps.

If the "Total transaction lifetime timeout" property for the application server, where the WebSphere BI Monitor is installed, is set to a value greater than 600 seconds, then you must add the following JVM property to the Application Server Generic JVM Properties and set its value to be the same as the one used in the "Total transaction lifetime timeout"
-Dmonitor.eventbus.locktimeout=<tx_timeout>
For example, if the Total transaction lifetime timeout is set to 660 seconds, then the JVM property must be added as follows:
-Dmonitor.eventbus.locktimeout=660
You must restart the WebSphere Application Server after adding this JVM property.

If the time zone of the operating system hosting the BI Monitor server supports daylight saving, add the following JVM property in the WAS Generic JVM Arguments and then restart the application server.
-Dmonitor.adjust4DST.enabled=true
If the time zone of the operating system hosting BI Monitor server does not support daylight saving, you do not need to use this JVM property.