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.
Check for updates to this topic (online)
Specify the type or types of failed events that you want to find.
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.
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 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.
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.
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.
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.
Note that the time is always local to the process server, not an individual machine running the administrative console.
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 example, 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.
The specified time is always local to the process server, not to an individual system that is running the administrative console.
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.
Specify the module from which an event originates. This field is available when you search for SCA events.
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.
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.
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.
You can search for events for which the event qualifier is declared. This field is available when you search for SCA events.
You can search for events that caused store to be started. This field is available when you search for SCA events.
Specify whether you want to search for events that are captured because the system was unable to send a failure response to a BPEL process. This field is available when you search for SCA events.
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.