Use the failed event manager to find and manage failed
events on all servers in a cell. The interface enables you to view
(and in some cases, edit) the data for a failed event, resubmit a
failed event, or delete a failed event.
The failed event manager handles the following types
of events:
- Service Component Architecture (SCA) failed events. In the context
of SCA, an event is a request or response that is received by an Advanced
Integration service application. It can come from an external source
(such as an inbound application adapter) or an external invocation
to a web service. The event consists of a reference to the business
logic it wants to operate and its data, stored in a Service Data Object
(a business object). When an event is received, it is processed by
the appropriate application business logic.
- Java Message Service (JMS) failed events. In the context of JMS,
a failed event is generated when a JMS data binding or function selector
operation fails, or when an exception occurs in a downstream component
and is thrown back to the JMS export or import. The Recovery service
handles failed events from JMS data bindings and MQ JMS data bindings.
- WebSphere MQ failed events. In the context of WebSphere MQ, a
failed event is generated when there is a problem (such as a data-handling
exception) in the WebSphere MQ or WebSphere MQ JMS binding export
or import used by an SCA module.
- Business Process Choreographer stopped, terminated,
and failed events. In the context of Business Process Choreographer,
exceptions can occur that, if not handled by the process logic, cause
an activity to stop or the process instance to fail. A failed event
is generated when a long-running Business Process Execution Language
(BPEL) process fails and one of the following happens:
- The process instance enters the Failed or Terminated state
- An activity enters the Stopped state
- Business Flow Manager hold queue events. You can
use the failed event manager to manage navigation messages that are
stored in the Business Flow Manager hold queue. A navigation message
might be stored in the hold queue if:
- An infrastructure, such as a database, is unavailable.
- The message is damaged.
Refer to the Business Process Management Information Center topics
on managing failed events for further details about the supported
event types.