Working with data in failed events

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 failed event has the following data associated with it:
  • The unique message ID and session ID for the event
  • The service invocation type between SCA components
  • The names of the module and component from which the event originated (the source). The failed event manager determines the source of an event based on the location where the invocation failed.
  • The names of the destination module, component and method for the event. The failed event manager determines the event's destination based on the location where the invocation failed.
  • The time the event failed
  • The exception thrown when the event failed
This data cannot be edited. In addition, failed events can have associated trace and expiration data, both of which can be edited.

Business data

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 is edited with the business data editor available in the failed event manager.

Related tasks
Browsing data in failed events
Editing trace or expiration data in a failed event
Editing business data in a failed event

Terms of use |

Last updated: Tue Feb 21 17:19:18 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)