Configuring System Monitor and Failed Event Manager to use Tomcat

This section describes how to configure System Monitor and Failed Event Manager to use Tomcat. For instructions on using WebSphere Application Server or WebSphere Application Server Express as the Web application server instead of Tomcat, see Configuring System Monitor and Failed Event Manager to use WebSphere Application Server or WebSphere Application Server Express. Before proceeding, ensure that you have Tomcat version 4.1.24 or 4.1.27 installed on your system.

Note:
Tomcat 4.1.24 and 4.1.27 are not supported in double byte character set language environments.

Configuring System Monitor to use Tomcat

To configure System Monitor to use Tomcat, follow these steps:

  1. Create the ICSMonitor directory under Tomcat_home/webapps (where Tomcat_home is the path of the Tomcat installation in your environment).
  2. Extract the WAR file contents into the ICSMonitor directory.
    Note:
    If you used the WebSphere Business Integration Server Express or Express Plus installer to install the product, the CWDashboard.war file is located in the ProductDir/WBSM directory.
  3. Copy the xerces.jar file from Tomcat_home/webapps/ICSMonitor/WEB-INF/lib to Tomcat_home/common/lib.
  4. Rename the xercesImpl.jar file, located in the Tomcat_home/common/endorsed directory, to xercesImpl.jar.old.
  5. Edit the setclasspath.sh file, located in the Tomcat_home/bin directory, by doing the following:

    1. Set the JAVA_OPTS property as follows:

      -DDASHBOARD_URL=http://HostName[:PortNumber]/ICSMonitor
      -DDASHBOARD_HOME=Tomcat_home/webapps/ICSMonitor
      -DORBNamingProvider=CosNaming
      -Dorg.omg.CORBA.ORBClass=com.ibm.CORBA.iiop.ORB
      -Dorg.omg.CORBA.ORBInitialPort=ORB_PORT
      -Dorg.omg.CORBA.ORBInitialHost=ORB_HOST
      -Dcom.ibm.CORBA.Debug.Output=stdout
      

      Important:
      The lines beginning with the characters -D all appear on separate lines to enable them to fit on the page. Insert only spaces, not line breaks, between the -D lines.
    2. Append the path to the db2java.zip file to the class path in setclasspath.sh. The db2java.zip file is located, by default, in the DB2_Installation_Dir/java directory.
  6. (Optional) Change the port number in the Tomcat_home/conf/server.xml file.

    The default port number is 8080.

  7. Run the following command:
    . /home/db2inst1/sqllib/db2profile
    
  8. Start Tomcat, as follows:
    Tomcat_home/bin/startup.sh
    

Configuring Failed Event Manager to use Tomcat

To configure Failed Event Manager to use Tomcat, follow these steps:

  1. Create the FailedEvents directory under Tomcat_home/webapps (where Tomcat_home is the path of the Tomcat installation in your environment).
  2. Extract the WAR file contents into the FailedEvents directory.
    Note:
    The FailedEvents.war file is located in the ProductDir/WBFEM/Tomcat directory.
  3. Copy the xerces.jar file from Tomcat_home/webapps/FailedEvents/WEB-INF/lib to Tomcat_home/common/lib.
  4. Rename the xercesImpl.jar file, located in the Tomcat_home/common/endorsed directory, to xercesImpl.jar.old.
  5. Edit the setclasspath.sh file, located in the Tomcat_home/bin directory, by doing the following:

    1. Set the JAVA_OPTS property as follows:

      -DFEM_HOME=Tomcat_home/webapps/FailedEvents
      -DORBNamingProvider=CosNaming 
      -Dorg.omg.CORBA.ORBClass=com.ibm.CORBA.iiop.ORB
      -Dorg.omg.CORBA.ORBInitialPort=ORB_PORT 
      -Dorg.omg.CORBA.ORBInitialHost=ORB_HOST
      -Dcom.ibm.CORBA.Debug.Output=stdout
      
      Important:
      The lines beginning with the characters -D all appear on separate lines to enable them to fit on the page. Insert only spaces, not line breaks, between the -D lines.
    2. Append the path to the db2java.zip file to the class path in setclasspath.sh. The db2java.zip file is located, by default, in the DB2_Installation_Dir/java directory.
  6. (Optional) Change the port number in the Tomcat_home/conf/server.xml file.

    The default port number is 8080.

  7. Run the following command:
    . /home/db2inst1/sqllib/db2profile
    
  8. Start Tomcat, as follows:
    Tomcat_home/bin/startup.sh
    

By default, security is enabled in the Tomcat 4.1.24 version of the Failed Event Manager. A user with the role of Administrator must be created in the Tomcat_home/conf/server.xml file so that the administrator can gain full access to the application. For details on how to create roles and use security in Failed Event Manager, refer to the System Administration Guide.

Copyright IBM Corp. 2004