Each failed event has data about the event to help you identify when and where the failure occurred. In addition, some types of failed events contain business data. You can browse the data for all failed events, and you can edit the trace, expiration, and business data for failed Service Component Architecture (SCA) events before resubmitting them.
By default, no trace occurs for an SCA event when the session calls an SCA service or executes a component. If you want to trace the event after you resubmit it, edit the value in the Trace Control field. Tracing can be set for a service or a component, and it can be output to a log. See the WebSphere Application Server Information Center for detailed information about trace settings.
Some failed SCA events have an expiration; if the event has expired, you cannot successfully resubmit it. To prevent a second failure, edit the expiration date to ensure that it is not expired when the event is resubmitted.
A failed SCA event can have both simple data and a business object associated with it. Use the business data editor to edit the simple data types (for example, String, Long, Integer, Date, Boolean). If a data type is complex (for example, an array or a business object), you must navigate through the business data hierarchy until you reach the simple data types that make up the array or business object.
To view and edit failed event data, use the following procedure.Links marked (online) require access to the Internet.
Check for updates to this topic (online)