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.
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.
Tomcat_home/bin/startup.bat
http://hostname:8080/FailedEvents.
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
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.