Steps for manually installing Failed Event Manager on Tomcat 4.1.24

Perform the following steps to manually install Failed Event Manager on Tomcat 4.1.24: Prior to beginning the steps below, ensure that WebSphere Application Server is running in Administrator mode on your environment.

  1. Under the Tomcat_home\webapps directory, create the FailedEvents directory, where Tomcat_home is the Tomcat installation path.
  2. Extract the FailedEvents.war file contents from the the \WBFEM\Tomcat directory into the Tomcat_home\webapps\FailedEvents directory.
  3. Open the setclasspath.bat file, located in Tomcat_home\bin directory and set the JAVA_OPTS property as follows:


    set JAVA_OPTS=-DFEM_HOME=C:\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%
    where %ORB_PORT% & %ORB_HOST% match what is in the ./bin/CWSharedEnv.bat file.

    Note:
    If Tomcat_home contains spaces, use quotes around the FEM_HOME value.
  4. Start Tomcat using the following command line to ensure that setclasspath.bat is called:


    Tomcat_home/bin/startup.bat

  5. With the application server running, start the Failed Event Manager by opening a browser window and entering the following URL:


    http://hostname:8080/FailedEvents.

    Note:
    8080 is the default port for the server. To change the port number, you must edit the Tomcat_home\conf\server.xml file and restart the application server.

Role-based security

The Failed Event Manager provides the ability to activate role-based security on WebSphere Application Server and Tomcat. Four basic roles exist for the Failed Events Manager.

The Administrator will create all but the default Administrator role, giving each View Failed Events permission at the server level. You may also create custom roles for use with the Failed Events Manager. For more information, see Creating custom roles for Failed Events Manager

Note:
You must use the SubmitEvents role along with another custom role that has permission to submit & delete failed events for collaborations and connectors at the component level. The ViewAll and ViewEvents roles can be used independently of another custom role.

Creating custom roles for Failed Events Manager

You can create custom roles in order to provide component level access. For example, using custom roles at a component level, you can restrict a user from viewing failed events that belong to a specific event owner, collaboration, or connector. Create custom roles using the Server Administration Tool in the System Manager., assigning View Failed Events permission at the server level. When creating roles at the component level, select the particular event owner, collaboration object or connector object and assign both Submit Failed Events and Delete Failed Events permission for each component.

Copyright IBM Corp. 1997, 2004