Configuring System Monitor and Failed Event Manager to use WebSphere Application Server or WebSphere Application Server Express

This section describes how to configure System Monitor and Failed Event Manager to use WebSphere Application Server or WebSphere Application Server Express. For instructions on using Tomcat instead, see Configuring System Monitor and Failed Event Manager to use Tomcat.

To configure System Monitor and Failed Event Manager to use WebSphere Application Server or WebSphere Application Server Express, you run a script supplied with WebSphere Business Integration Server Express and Express Plus. The script is called CWDashboard.sh and is located in the directory ProductDir/bin (where ProductDir represents the directory Home_directory/IBM/WebSphereServer by default). You can run this script to configure the tools to work with or without a Web server, such as IBM HTTP Web Server.

Before proceeding, ensure that you have installed WebSphere Application Server or WebSphere Application Server Express versions 5.0.2 or 5.1. (You can install WebSphere Application Server Express v5.1 from the WebSphere Business Integration Server Express or Express Plus Launchpad.) Then proceed to one of the following sections, depending on whether you want to use your installation with a Web server:

Configuring System Monitor and Failed Event Manager when using a Web server

WebSphere Application Server is supplied with a Web server; WebSphere Application Server Express is not. If you are using WebSphere Application Server Express and want to use a Web server, you must obtain and install the IBM HTTP Server (available for free from the IBM Web site) and the Web server plug-in for WebSphere Application Server Express. See the WebSphere Application Server Express documentation for more information.

To configure System Monitor and Failed Event Manager to use a Web server, perform the following steps:

  1. Run CWDashboard.sh with the following parameters:

    Here is an example command:

    Home_directory/IBM/WebSphereServer/CWDashboard.sh        \
    "opt/IBM/WebSphere/Express502/AppServer"                 \
    hostname.ibm.com "Home_directory/IBM/WebSphere/Server"   \
    "DB2_Installation_Dir/java" y
    
    Important:
    Certain steps in this procedure show commands broken on one or more lines. These line breaks were inserted to enable the text to fit on the page. When typing the actual commands, insert spaces at these points, not line breaks.
  2. From the WebSphere Administrator's Console (accessible from a Web browser on a remote Windows machine), expand Environment in the left navigation pane, select the Update Web Server Plugin link, and select OK.
  3. If the ICSMonitor Application Server is started, stop it:
    /opt/IBM/WebSphere/Express502/AppServer/bin/stopServer.sh ICSMonitor
    
  4. Run the following command:
    . /home/db2inst1/sqllib/db2profile
    
  5. Start the ICSMonitor Application Server:
    /opt/IBM/WebSphere/Express502/AppServer/bin/startServer.sh ICSMonitor
    
  6. To access System Monitor, type the URL:
    http://hostname/ICSMonitor
    

    where hostname is the name of the computer on which WebSphere Application Server or WebSphere Application Server Express is installed.

  7. To access Failed Event Manager, type the URL:
    http://hostname/FailedEvents
    

    where hostname is the name of the computer on which WebSphere Application Server or WebSphere Application Server Express is installed.

Configuring System Monitor and Failed Event Manager when not using a Web server

If you are not using a Web server with your installation, you must configure System Monitor and Failed Event Manager to use a different port number. Do the following:

  1. Run ProductDir/bin/CWDashboard.sh with the following parameters:

    Here is an example command:

    Home_directory/IBM/WebSphereServer/CWDashboard.sh         \ 
    "/opt/IBM/WebSphere/Express502/AppServer"                 \ 
    hostname.ibm.com "Home_directory/IBM/WebSphereServer      \
    "DB2_Installation_Dir/java" n 7089 7043
    
    Important:
    Certain steps in this procedure show commands broken on one or more lines. These line breaks were inserted to enable the text to fit on the page. When typing the actual commands, insert spaces at these points, not line breaks.
  2. If the ICSMonitor Application Server is started, stop it:
    /opt/IBM/WebSphere/Express502/AppServer/bin/stopServer.sh ICSMonitor
    
  3. Run the following command:
    . /home/db2inst1/sqllib/db2profile
    
  4. Start the ICSMonitor Application Server:
    /opt/IBM/WebSphere/Express502/AppServer/bin/startServer.sh ICSMonitor
    
  5. To access System Monitor, type the URL:
    http://hostname:portnumber/ICSMonitor
    

    where hostname is the name of the computer on which WebSphere Application Server or WebSphere Application Server Express is installed.

  6. To access Failed Event Manager, type the URL:
    http://hostname:portnumber/FailedEvents
    

    where hostname is the name of the computer on which WebSphere Application Server or WebSphere Application Server Express is installed.

Copyright IBM Corp. 2004