=====================================================================================
IBM® WebSphere® Business Integration (BI) Monitor™ v4.2.4 Fix Pack3
- Patch3 Readme File
=====================================================================================
© Copyright International Business Machines Corporation. 2002, 2004. All rights reserved.
This file contains the new updates and fixed bugs in the IBM WebSphere BI Monitor v4.2.4 Fix Pack3 - Patch3. Refer to the file named install_fix_pack3_patch3.html for the information and steps required for installing IBM WebSphere BI Monitor v4.2.4 Fix Pack3 - Patch3.
The BI Monitor v4.2.4 Fix Pack3 - Patch3 provides the following new updates:
BI Monitor v4.2.4 Fix Pack3 Patch3 Supports now using Automatic installation on an already federated WAS servers in Network Deployment environment. The automatic installation wizard has been updated to contain the following changes:
A new installation step has been added to ask the user to select the WebSphere Application Server type on which the Monitor will be deployed. The user can select either the IBM WebSphere Application Server or the IBM WebSphere Deployment Manager for Network Deployment. Based on the user selection the wizard will continue as the following:
When you are deploying the Monitor using the Deployment Manager to a node that exist in a remote machine other that the Deployment Manager machine, then the following fields must be entered with the values of the remote node environment:
Database JDBC driver
Monitor database name/Alias
Monitor database User Name and Password
IBM MQSeries Workflow library path and file name
MQ Workflow database name/Alias
MQ Workflow database User Name and Password
In this case you must disable the wizard to check/validate the existence of 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%\lib\j2ee.jar;%WAS_HOME%\lib\admin.jar;%WAS_HOME%\lib\wsexception.jar;%WAS_HOME%\lib\wasjmx.jar;WBIMonitor424-FixPack3.jar 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:WBIMonitor424-FixPack3.jar run
Important Note: In case you choose to install and deploy the BI Monitor on a Network deployment environment then the Deployment Manager must be started and running at installation time.
The BI Monitor v4.2.4 Fix Pack3 - Patch2.3 provides the following new updates:
Support for Oracle 9.2.0.1 Database Server.
Support for WebSphere MQ Workflow v3.5.
Support for WebSphere Portal Server (WPS) v5.0.2.1, with the following specifications:
APAR JR20646: Fixed the bug that caused the Workflow Dashboard to give empty Business Measure Value when the used Location is at the first activity inside a Block.