WebSphere

Failed Event details (SCA events)

Use the Failed Event details page to view data for a single failed SCA event and to perform tasks such as deleting, resubmitting, modifying, and setting trace for the event.

To access this page in the console, click Integration Applications > Failed Event Manager , perform a search for failed SCA events, and click the name of a specific event listed in the Search Results page.

The Failed Event details page provides the event ID, session ID and event sequencing status associated with the failed event, as well as information about the event's source, destination, time of failure, and cause of failure.

In addition to viewing a failed event's data, you can perform the following tasks from this page:

Event type

Specifies the type of event that failed. The value is SCA for all failed SCA events.

The event type is assigned automatically by the Recovery subsystem; you cannot edit it.

Event status

Specifies the status of the failed event. For SCA events, the only available status type is Failed.

The event status is assigned automatically by the Recovery subsystem; you cannot edit it.

Event ID

Specifies the unique ID for the failed event. This ID persists even after the event is resubmitted; if the resubmission fails, the event is returned to the failed event manager with the same event ID.

The event ID is assigned automatically by the Recovery subsystem; you cannot edit it.

Session ID

Specifies the unique session ID for the failed event.

Every event executes within a session; the session includes all of the information needed to process an event. If an event fails, the failed event manager encapsulates specific session information for the failed execution branch in the Session ID parameter.

Note that any Common Base Events and business process instances related to a particular failed event are all linked by the same session ID, making it easy to identify and examine them for additional information about the failure.

A session ID is assigned automatically by the Recovery subsystem; you cannot edit it.

Interaction type

Specifies the type of service invocation between SCA components. The three supported invocation models are asynchronous request/deferred response, asynchronous request with callback, and asynchronous one-way.

You cannot edit this field.

Source module

Specifies the name of the module from which the event originated.

You cannot edit this field.

Source component

Specifies the name of the component from which the event originated.

You cannot edit this field.

Destination module

Displays the name of the destination module for the event (where the event was going when it failed).

You cannot edit this field.

Destination component

Displays the name of the destination component for the event (where the event was going when it failed).

You cannot edit this field.

Destination method

Displays the name of the destination method for the event.

You cannot edit this field.

Failure time

Displays the date and time the event failed. The time shown is local to the process server, and the value is formatted for the current locale.

You cannot edit this field.

Deployment Target of Failure

Displays the deployment target for the event. Its value includes the name of the target node, server, and cluster (if applicable).

You cannot edit this field.

Exception text

Displays the text of the exception that was generated when the event failed.

You cannot edit this field.

Resubmit expiration time

Specifiy the amount of time that can elapse before a failed event expires and can no longer be resubmitted. The time shown is local to the process server.

If a user specifies an expiration with the asynchronous call that sent the event, that expiration data persists even if the event fails, and the expiration time appears in the Resubmit expiration time field.

You can edit this field to specify a new expiration time for the failed event. The value for this field must be a date and time formatted for your locale. A locale-appropriate example is provided above the field.

Trace control

Specify the level of tracing to be used on a resubmitted event.

If you have already set tracing on the failed event, the Trace control field displays that value. Otherwise, it displays the suggested default value of SCA.LOG.INFO;COMP.LOG.INFO, which specifies that no trace occurs when the session calls an SCA service or executes a component.

You can edit this field to assign a different trace level for the failed event. Tracing can be set for a service or a component, and it can be output to a log or the Common Event Infrastructure (CEI) server. For detailed information about setting and viewing trace, see the Monitoring topics in the WebSphere Business Process Management Information Center.

Event sequencing qualified

Specifies whether the event sequencing qualifier has been defined for the failed event.

The following values are valid for the field.
  • True: Event sequencing has been declared for this event. If the event sequencing qualifier's ContinueOnError attribute has been set to False, no dependent events are processed until the failure is resolved.
  • False: Event sequencing has not been declared for this event.
  • Not Available: Event sequencing is not supported for this event type.

topic Topic topic

Terms of use | Feedback


Timestamp icon Last updated: 26 July 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wbpmhelp.620.doc/com.ibm.ws.console.wbi.wbifailedeventmanager/fem_detailform.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).