Failed Event Manager allows you to view and manage failed events from the Web.
Failed Event Manager works with IBM WebSphere Application Server or with Tomcat. For information on installing Failed Event Manager to work with WebSphere Application Server or Tomcat, refer to the WebSphere Business Integration Server Express Installation Guide. Failed Event Manager works with the following versions of WebSphere Application Server, WebSphere Application Server Express, and Tomcat:
If you selected an Administrative Toolset installation of WebSphere Business Integration Server Express, Failed Event Manager is automatically installed and configured if WebSphere Application Server or WebSphere Application Server Express versions 5.0.2 or 5.1 are detected on your system.
By default, role-based security is enabled after you have installed Tomcat with Failed Event Manager (Refer to the WebSphere Business Integration Server Express Installation Guide). Default roles mentioned above must be added in Tomcat_home\conf\tomcat-users.xml directory. Creating a user with the Administrator role allows that user to gain full access to Failed Event Manager. For details on how to create roles in Failed Event Manager, refer to Steps for creating custom users and roles for Failed Event Manager with Tomcat
Role-based security is available if you are using Tomcat with Failed Event Manager. The actions you can perform with those failed events depends on role-based security. Administrators can assign users one or more of four default roles, and administrators have permission to create custom roles for your specific team using Application Assembly Tool. The following default roles are included:
This section includes the following procedures:
Perform the following steps to create custom users and roles if you are using Tomcat:
<auth-constraint id="AuthConstraint_1062537631424"> <description>SC1:+:</description> <role-name>Administrator</role-name> <role-name>ViewEvents</role-name> <role-name>ViewAll</role-name> <role-name>SubmitEvents</role-name> <role-name>Manager</role-name> </auth-constraint>
<security-role id="SecurityRole_1068513225089"> <description>Can manage all events.</description> <role-name>Manager</role-name> </security-role>
<servlet id="Servlet_1062537018298"> <servlet-name>Login</servlet-name> <display-name>Login</display-name>
<servlet-class> com.ibm.btools.itools.FailedEvents.servlets.Login </servlet-class> <init-param id="InitParam_1063835207426"> <param-name>ROLECOMPONENTS</param-name> <param-value> role1: event_owners SourceToDestCollab |role2:event_owners=Collab2* bos=CUSTOMER2.Create#2/4 |role3:event_owners=SourceToDestCollab, Collab2 </param-value> <description> Roles and components (collabs or connectors) associated with these roles. </description> </init-param> </servlet>
The parameter value is a string in the following format:
<RoleName1>:event_owners=<ownername>*connectors=<connectorName> *bos=<boname.verb> #<CompositeKeyValue>+<CompositekeyValue2>/ <AnotherPossibleKeyValue> | <RoleName2>: .....
Where:
< | > - separates two roles
< : > - separates the role name from components of the role
< * > - separates components within a role, for example, connectors and business objects
< = > - separates the component name from its values
< , > - separates values within a component
< # >- separates business object name from its key values
< / >- separates different possible keys of a business object
< + >- separates the composite key of a business object (two or more primary keys)
For example:
Role1:event_owners=collab1, collab2*connectors=conn1, conn2*bos=bo1.create#55/67, bo2.delete#99/80 |
Role2:event_owners=collab3,collab4*connectors=conn3 *bos= bo4.create#59+9876/82, bo2.delete#56
In this example, "event_owners" refers to point of failure of the event, either at the collaboration or at the connector.
Perform the following steps to log on to Failed Event Manager:
http://HostName/FailedEvents
where HostName is the name of the computer on which WebSphere Application Server is installed.
http://HostName:nnnn//FailedEvents
where HostName is the name of the computer on which WebSphere Application Server is installed and nnnn is the port number.
Figure 61. Failed Event Manager Connect screen
After you log on, the Query dialog box appears, as shown in Figure 62.
Perform the following steps to view information about failed events in Failed Event Manager:
A Table of Failed Events appears, as show in Figure 63.
Figure 63. Failed Event Manager Table of Failed Events
If you are not assigned to one of the roles that has access to viewing business objects, the business object buttons may not be available in this table, as shown in Figure 64.
Figure 64. Failed Event Manager Table of Failed Events without rights to view business objects
The Event Details dialog box appears, as shown in Figure 65.
Figure 66. Failed Event Manager Business Object Data dialog box
Perform the following steps in a Table of Failed Events to process failed events:
Perform the following steps to check the roles you are assigned for Failed Event Manager role-base security:
A page appears listing the default roles available. You can type a role name to see if you are assigned to that role.