Failed event search

Locate failed events that meet specified criteria.

To view this page in the administrative console, click Integration Applications > Failed Event Manager > Search failed events.

The page contains fields that are common to all event types, as well as fields that are specific to each type of event that is handled by the Recovery subsystem. These type-specific fields display only when you search for the related event type. The following sections describe all the fields available on the page.


Links marked (online) require access to the Internet. Each link launches a search for the topic in the online information center. When search results are listed, select the topic that corresponds best to your configuration.

Check for updates to this topic (online)

Event type

Specify the type or types of failed events that you want to find.

Select one or more of the following check boxes:
  • SCA: Search for failed Service Component Architecture (SCA) events. If you select this option and do not specify other search criteria, the search returns all failed SCA events.
  • JMS: Search for failed Java Message Service (JMS) events. If you select this option and do not specify other search criteria, the search returns all failed JMS events.
  • MQ: Search for failed WebSphere MQ events. If you select this option and do not specify other search criteria, the search returns all failed WebSphere MQ events.
  • BPC: (WebSphere Process Server only) Search for failed, stopped, or terminated Business Process Choreographer events. If you select this option and do not specify other search criteria, the search returns all failed Business Process Choreographer events.
  • BFMHold: (WebSphere Process Server only) Search for Business Flow Manager hold queue events. If you select this option and do not specify other search criteria, the search returns all failed hold-queue events.

Event status

Specify the event status that you want to include in your search. This field is available only when you are searching for Business Process Choreographer events. If you are searching for SCA, JMS, WebSphere MQ, or Business Flow Manager hold queue events only, the value defaults to failed and the field is unavailable.

Select one or more of the following check boxes:
  • Select all: Search for all failed, stopped, and terminated events. Clear this check box if you want to limit your search to one or two states.
  • failed: Search for all Business Process Execution Language (BPEL) processes that have failed with a process instance state of failed.
  • terminated: Search for all BPEL processes that have failed with a process instance state of terminated.
  • stopped: Search for all BPEL processes that have failed with one or more activities in the stopped state.

Module

Specify the failed event destination module (the module to which the event is sent). This field is only available when you search for SCA, JMS, WebSphere MQ, Business Flow Manager hold queue, and Business Process Choreographer events.

The destination is determined by the failed event manager from the perspective of the failure point. To clarify how the destination is determined, in the following example, Component A asynchronously invokes Component B. The request message is sent from A to B, and the response message is sent from B to A.
  • If the exception occurs during the initial request, Component A is the source and Component B is the destination for the purposes of the failed event manager.
  • If the exception occurs during the response, Component B is the source and Component A is the destination for the purposes of the failed event manager.

The Module field accepts the asterisk (*) wildcard character. Values are case-sensitive. If you leave this field blank, it is treated as a wildcard and all destination modules are returned.

Component

Specify the failed event destination component (the component to which the event is sent). This field is available when you search for all event types.

The destination is determined from the perspective of the failure point. (See the description for the Module field for more information on how the destination is determined.)

The Component field accepts the asterisk (*) wildcard character. Values are case-sensitive. If you leave this field blank, it is treated as a wildcard and all destination components are returned.

Operation

Specify the failed event's operation (the method designated to process the event). This field is available when searching for all event types.

The destination is determined from the perspective of the failure point.

The field accepts the asterisk (*) wildcard character. Values are case-sensitive. If you leave this field blank, it is treated as a wildcard and all destination methods are returned.

From date

To search for events that failed during a particular time period, specify the starting date and time. This field is available when you search for all event types.

The value for this field must conform to the time and date format that is required by your computer locale. For example, the required format for the en_US locale is MM/DD/YY HH:MM Meridiem; a correctly formatted value for the en_US locale is12/20/2005 4:30 PM. The page contains an example of the appropriate format for your locale above the field.

Note that the time is always local to the process server, not an individual machine running the administrative console.

To date

Specify the ending date and time when searching for events that failed during a particular time period. This field is available when searching for all event types.

The value for this field must conform to the time and date format required by your computer's locale. (For instance, the required format for the en_US locale is MM/DD/YY HH:MM Meridiem; a correctly formatted value looks like 12/20/2005 8:30 PM.) The page contains an example of the appropriate format for your locale above the field.

The specified time is always local to the process server, not to an individual system that is running the administrative console.

Session ID

Specify the ID for the session in which you want to search. This field is available when you search for SCA events.

Every event executes in a session; the session includes all of the information that is 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.

Source module

Specify the module from which an event originates. This field is available when you search for SCA events.

The source is determined from the perspective of the failure point. To help clarify how the source is determined, consider the following example, where Component A is asynchronously invoking Component B. The request message is sent from A to B, and the response message is sent from B to A.
  • If the exception occurs during the initial request, Component A is the source and Component B is the destination for the purposes of the failed event manager.
  • If the exception occurs during the response, Component B is the source and Component A is the destination for the purposes of the failed event manager.

The field accepts the asterisk (*) wildcard character. Values are case-sensitive. If you leave this field blank, it is treated as a wildcard and all source modules are returned.

Source component

Specify the component from which an event originated. This field is available when searching for SCA events.

The source is determined from the perspective of the failure point. See the description for the Source module field for more information on how the source is determined.

The Source component field accepts the asterisk (*) wildcard character. Values are case-sensitive. If you leave this field blank, it is treated as a wildcard and all source components are returned.

Business object type

To search for events that contain a specific business object type, specify the type. This field is available when you search for SCA events.

The Business object type field accepts the asterisk (*) wildcard character. Values are case-sensitive. If you leave this field blank, it is treated as a wildcard and all events are returned.

Event sequencing qualifier

You can search for events for which the event qualifier is declared. This field is available when you search for SCA events.

Select one of the following options from the menu:
  • Sequenced: Search for events that are part of an event sequence
  • Not sequenced: Search for events that are not part of an event sequence. Event ordering is not required for this event.
  • Blank: Do not include the event sequencing qualifier as part of your search criteria.

Store initiator qualifier

You can search for events that caused store to be started. This field is available when you search for SCA events.

Select one of the following options from the menu:
  • Store initiator: Search for events that initiated event storing. Follow-up events for the same event destination will be stored based on the destination's availability. Events can be forwarded when the destination becomes available.
  • Not a store initiator: Search for events that did not initiate event storing.
  • Blank: Do not include the store-and-forward qualifier as part of your search criteria.

Process response qualifier

(WebSphere Process Server only) Specify whether you want to search for events that are captured because the system was unable to send a failure response to a business process. This field is available when you search for SCA events.

Select one of the following options from the menu:
  • Process response: Search for events that are a response for a process. The event can be forwarded to the target process or resubmitted to the caller when resubmitting failed events.
  • Not a process response: Search for events that are not a response for a process. The event will be resubmitted to the caller when resubmitting failed events.
  • Blank: Do not include the process-response qualifier as part of the search criteria.

Exception text

To search for exception text in failed events, specify the text. This field is available when you search for SCA events.

You can specify all of the text that appears in the exception, or specify a fragment of it the asterisk (*) wildcard character. Values are case-sensitive. If you leave this field blank, it is treated as a wildcard and all events are returned.