Use the Search Results page to view a list of failed events
on a standalone server or on all the servers in a cell. The list can
include either all failed events or a subset of failed events that
have been retrieved during a criteria-based search.
To access this page in the console, click Integration
Applications > Failed Event Manager > Get all failed events or
perform a criteria-based search.
Failed events are displayed in a table, along with the following
information. Note that not all information is relevant for all event
types; when an event is not associated with a particular type of information,
the table cell is blank.
- Event ID: The unique ID for the event.
- Event type: The type of failed event (SCA,
JMS, WebSphere MQ, Business Flow Manager hold queue, or Business Process
Choreographer).
- Module: The module designated to receive the event.
- Component: The component designated to receive the event.
- Operation: The method designated to process the event.
- Failure time: The time the event failed. Note that the time is
local to the machine on which the process server is running.
- Event status: The status of the event. SCA,
JMS, WebSphere MQ, and hold queue events always have a status of failed.
Business Process Choreographer events can be in the Failed, Stopped,
or Terminated state.
- Event qualifier: The type of qualifier associated
with the failed event. Events can have one of the following qualifiers:
- Sequenced: The event is part of an event
sequence. This qualifier requires that the event order be kept when
processing events. If the ContinueOnError attribute of the event sequence
qualifier is set to false, no dependent events are processed until
the failure is resolved.
- Store initiator: The event initiated event
storing. Follow-up events for the same event destination will be stored
based on the destination's availability. Events can be forwarded when
the destination becomes available.
Process response: The
event is a response for a process. The event can be forwarded to the
target process or resubmitted to the caller when resubmitting failed
events.
- Sequenced, Store initiator: The event is
part of an event sequence. This qualifier requires that the event
order be kept when processing events. If the ContinueOnError attribute
of the event sequence qualifier is set to false, no dependent events
are processed until the failure is resolved. The event initiated event
storing. Follow-up events for the same event destination will be stored
based on the destination's availability. Events can be forwarded when
the destination becomes available.
Sequenced, Process response:
The event is part of an event sequence. This qualifier requires that
the event order be kept when processing events. If the ContinueOnError
attribute of the event sequence qualifier is set to false, no dependent
events are processed until the failure is resolved. The event is a
response for a process.
Click the up or down arrows at the top of any column to sort
the contents of that column in either ascending or descending order.
A row of buttons on the top of the table provides administrative
functionality for failed events. The following table describes each
button:
Button |
Function |
Refresh |
Refreshes the current display. |
Get all |
Retrieves and displays all failed events in the
cell. |
New search |
Opens the Search page so that you can perform a
criteria-based search for a subset of failed events. |
Resubmit |
Resubmits one or more failed events. For each
failed event that you want to resubmit, click the check box in the
Select column. The Resubmit button works only on selected failed
events.
|
Resubmit with trace |
Resubmits one or more failed SCA events with trace
enabled. For each failed SCA event that you want to resubmit with
trace, click the check box in the Select column. The Resubmit with
trace button works only on selected failed events. Note: You cannot
resubmit JMS or Business Process Choreographer events with trace enabled.
|
Delete |
Deletes one or more failed
events. For Business Process Choreographer events, all associated
process instances are also deleted.
For each failed event you
want to delete, click the check box in the Select column. The Delete button
works only on selected failed events.
|
Delete expired events |
Deletes all expired failed events. A failed
SCA or JMS event can have an expiration time associated with it. If
a failed event has an expiration set, it must be resubmitted before
it expires.
|
Clear all |
Deletes all failed events
on the application server. If you have failed Business Process Choreographer
events, all associated process instances are deleted.
|
Links marked (online) require access to the Internet.
Each link launches a search for the topic in the online information center.
When search results are listed, select the topic that corresponds best to
your configuration.