Each failed event has data associated with it; often, that data
can be edited before an event is resubmitted. There are two basic types of
data for a failed event: data about the event, and business data.
Data about the failed event
Each type of failed
event has the following data associated with it:
- SCA events
- The event ID, type, status, and session ID
- The service invocation type between SCA components
- The names of the module and component from which the event originated
(the source).
- The names of the destination module, component and method for the event
- The time the event failed
- The deployment target associated with the event
- Whether an event sequencing qualifier has been declared for this event
- The destination module where the event has been or will be resubmitted
- The correlation ID, if one exists
- The exception thrown when the event failed
- The expiration date for resubmitted events (this data can be edited)
- The trace control set for the event (this data can be edited)
- JMS events:
- The event ID, type, and status
- The interaction type
- The names of the destination module, component and method for the event
- The time the event failed
- The deployment target associated with the event
- The exception thrown when the event failed
- The destination module where the event has been or will be resubmitted
- The correlation ID, if one exists
- The expiration date for resubmitted events (this data can be edited)
- The JMS-specific properties associated with the failed event: redelivered
count, delivery mode, message priority, type, replyTo destination,
and redelivered indicator (true or false).
Business data
SCA
failed events typically include business data. Business data can be encapsulated
in a business object, or it can be simple data that is not part of a business
object. Business data for SCA failed events can be edited with the business
data editor available in the failed event manager.