Browsing and editing data in failed events

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.

Before you begin

If administrative security is enabled, you must be logged as administrator or operator to perform this task.

About this task

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.

Procedure

  1. Ensure that the failed event manager is open and that you have retrieved a list of the failed events on your system.
  2. From the Search Results page, click the failed event ID.

    The Failed Event Details page opens and displays all of the information about the event.

  3. To edit the trace or expiration data for an SCA event, perform the following steps. Note that any edits you make to the trace or expiration data are only saved locally until you resubmit the event. If you perform any other action before resubmitting the event, all edits are lost.
    1. If the event has an expiration date that causes it to expire before it is resubmitted, edit the expiration in the Resubmit expiration time field.

      The expiration time shown is local to the server. The value for this field must be formatted according to your specified locale.

    2. If you want to enable tracing for the failed event, specify a new value in the Trace Control field. For detailed information about trace values, see the monitoring topics in the IBM Business Process Management Information Center.
    3. Resubmit the event.
  4. If your failed event has business data, you can browse it by clicking Edit business data.

    The Business Data Editor collection page opens, displaying the business data associated with the failed event. Each parameter name in the hierarchy is a link. If the parameter is a simple data type, clicking its name opens a form so you can edit the parameter's value. If the parameter is a complex data type, clicking its name expands the hierarchy further.

  5. To modify business data, update the value in the Parameter value field, and then resubmit the event.

Links marked (online) require access to the Internet.

Check for updates to this topic (online)