This chapter provides a step-by-step procedure that guides you through Installing IBM WebSphere Business Integration (BI) Monitor with all its components and deploying the Monitor Server on Windows, AIX and Solaris platforms. The chapter also contains the procedures of un-deploying the Monitor Server and how to completely uninstall BI Monitor. At this stage, it is assumed that all the prerequisite software has been installed, and the Monitor and Event Queue databases have been created and configured successfully.
The following conventions are used for all the instructions throughout this document:
<WebSphere> : The WebSphere home directory. e.g. C:\WebSphere
<MQ> : The MQ Workflow home directory. (For example: C:\WebSphere\AppServer on Windows platform, /usr/WebSphere/AppServer on AIX platform, or /opt/WebSphere/AppServer in Solaris platform).
<DB2> : The DB2 home directory. (For example: C:\SQLLIB)
<Oracle> : The Oracle home directory on the Oracle Server machine (if Oracle is not running on the same machine on which the IBM WebSphere Application Server is installed). For example: C:\oracle\ora81 (Local) or \\oracle_machine\oracle\ora81 (Network)
<Monitor> : The Monitor installation directory. (For example: C:\WBIMonitor)
<WebServerName> : The name of the machine that hosts the Web server for which the WebSphere is configured. (For example: The machine name on which the IBM HTTP Server or Microsoft IIS 4.0 or IIS 5.0 is installed)
<ServerName> : The name of the server on which the Monitor will be installed.
<WebPath> : The monitor web application web path (For example: /monitor).
Important Notes:
On AIX and Solaris platforms, use forward slash / instead of back-slash \ when writing paths.
The names and paths of folders and files are case sensitive.
The names and paths of folders and files that you will specify during the installation should not contain any spaces. (For example, the Monitor installation directory, the WebSphere home directory, and/or the DB2 home directory)
Make sure that the user account you are using have all needed permissions. For example, using a user account who has no permissions on WebSphere or the Database will fail to install and deploy the monitor.
On AIX 5.1 platform, the environment variable named LIBPATH must be appended with the following paths: <MQ>/lib and <MQ>/lib/mqserver. To do this, type the following command in the console window from which you will start the WebSphere and then press Enter:
export LIBPATH=$LIBPATH:<MQ>/lib:<MQ>/lib/mqserver
The Monitor will not work if the server properties client.encoding.override or default.client.encoding are set to any encoding other than UTF-8.
If you are using WebSphere Application Server 4.0.5, the property client.encoding.override=UTF-8 should be added explicitly in the server JVM's settings. This must be done manually after you finish the deployment if you performed the deployment automatically using the BI Monitor Installation Wizard as in the following steps:
Open Administrator's console
Select the Monitor Server from the Application servers
Select the JVM Settings tab
In the System Properties list, click Add
Type client.encoding.override as the property name.
Type UTF-8 as the value.
Click apply and restart the server
Make sure to increase the parameter named Statement Cache Size of the connection pool for all Data Sources that are created after successful deployment. The default value for WebSphere Application Server 4.x is 100 which is suitable for single threaded event processor. You should increase it to enhance the system performance if you plan to configure multiple event processors. The default value for WebSphere Application Server 5.x is 10 which must be increased to 100 if you plan to use single threaded event processor or to more than 100 if you plan to configure multiple event processors.
******************************************************************