WebSphere

Search

Use the Search page to locate only those failed events that meet specified criteria.

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

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

Event type

Specify the type or types of failed events 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 any additional 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 any additional search criteria, the search returns all failed JMS events.
  • BPC: Search for failed, stopped, or terminated Business Process Choreographer events. If you select this option and do not specify any additional search criteria, the search returns all failed Business Process Choreographer events.
  • BFMHold: Search for Business Flow Manager hold queue events. If you select this option and do not specify any additional search criteria, the search returns all failed hold queue events.

Event status

Specify the event status 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, 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’s destination module (the module to which the event was being sent). This field is available when searching for SCA, JMS, Business Flow Manager hold queue, and Business Process Choreographer events.

The destination is determined from the perspective of the failure point. To help clarify how the destination 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 wild card and all destination modules are returned.

Component

Specify the failed event’s destination component (the component to which the event was being sent). 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 wild card 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 wild card and all destination methods are returned.

From date

Specify the starting 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 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 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.

Session ID

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

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.

Source module

Specify the module 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. 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 wild card 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.

See the description for the Source module field for more information on how the source is determined.

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

Business object type

Specify a business object type when searching for failed events that contain a particular business object type. This field is available when searching 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 wild card and all events are returned.

Event sequencing qualified

Specify whether you want to search for events with the event sequencing qualifier declared. This field is available when searching for SCA events.

Select one of the following options from the drop-down menu:
  • True: Search for events that have the event sequencing qualifier declared.
  • False: Search for events that do not have the event sequencing qualifier declared.

Exception text

Specify the exception text you want to search for within the failed events. This field is available when searching for SCA events.

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


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_searchform.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).