This appendix describes the manual steps of deploying BI Monitor on IBM WebSphere 6.0. Before starting these steps, it is assumed that the Monitor Database (and Event Queue Database if you are using MQ Workflow as your engine) with the required Table Spaces are created and configured in your Database Server. The following conventions are used for all the instructions throughout this document:
<WebSphere_Profiles>: WebSphere profile directory. e.g. C:\IBM\WebSphere\AppServer\profiles
<Profile_Name>: WebSphere profile name home directory.
<MQ>: The MQ Workflow home directory. (e.g. c:\IBM\WebSphereMQWorkflow on Windows platform, /user/fmc on AIX platform, or /opt/fmc on Solaris platform)
<MQ Series>: The WebSphere MQ Series home directory. (e.g. c:\MQSeries on Windows platform, /usr/mqm on AIX platform, or /opt/mqm on Solaris platform)
<DB2>: The DB2 home directory. e.g. 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). e.g. c:\oracle\ora81 (Local) or \\oracle_machine\oracle\ora81 (Network)
<Monitor>: The Monitor installation directory where the BI Monitor has been installed. e.g. c:\WBIMonitor
<ServerName>: The name of the server on which the Monitor will be installed.
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.
Make sure that the user name you are using has all needed permissions. For example, using a user who has no permissions on WebSphere or the Database will fail to 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.