Selection Criteria in the Message Monitor

Standard Selection

On the Standard Selection tab, you can either select messages based on a set of message or sequence IDs, or based on a time range with optional addition of message attribute values. If you do not enter any additional selection criteria, the default time range of one hour back until the end of the day is used. The attributes for time range-based selection are either direct message attributes such as adapter type, user name or sender/receiver party and interface name, or the processing status group.

You can select one of the following adapter types:

• Plain SOAP

  non-WSRM based SAP reliable messaging

• Groupware Scenario

  Web services sent and received within a groupware scenario, where messages from the consumer are "pulled" from the provider.

• Mapping

  Web services that originate from mappings

• Eventing

  publish/subscribe mechanism which is based on WS messages

• Standard Web service

  native Web services

• Shortcut

  local Web services that are called in a performance optimized way

• Integration Server

  in an XI environment, messages from integration server

• RFC

  synchronous RFC consumers

  Note

  RFC consumers can currently only be used as target consumers in single-target consumer mappings (STCM). For more information, see Creating RFC Consumers for Single-Target Consumer Mappings.

The processing status describes whether there are problems in the processing of a message. It is a derived message attribute that combines the native message state, the sequence state, the asynchronous processing queue (bgRFC queue) state. For on-failure, it includes the respective state as well. All of these statuses are considered when making a statement about the overall status of the message.

For easier management of the processing statuses, they are consolidated into the following processing status groups:

• Application error

  An error that occurred in the application that implements a service provider.

• System error

  An error that occurred in the message processing infrastructure.

• Erroneous

  A combination of the groups Application error and System Error.

• Terminated with dump

  An error that produced a short dump during message processing.

• Wait for processing

  The message is waiting for processing. The reason for this might be that the message is not the first in the processing queue of a sequence. In that case, all predecessors need to be processed first. It can also indicate an overload situation preventing a fast processing of messages.

• Incomplete processing

  A combination of the groups Application error, System error and Wait for processing.

• Incomplete (no "pulling"-messages)

  All incomplete messages, but does not include any messages pulled from the consumer by the provider (used in groupware scenarios).

• Canceled

  The message was manually canceled or it is an automatically annulled compensate message in TUC/C communication.

• Isolated

  The logical port of the message is isolated. Therefore, the message will not be sent to the service provider system.

• Canceled or isolated

  A combination of the groups Canceled and Isolated.

• Finished

  The message was successfully processed.

Prerequisites for User-Defined Selection

To use the user-defined selection, you must be authorized to display the message payloads. This means you must be assigned a role with the authorization object S_SRT_MONI with activity 29 or 36.

The search values for the user-defined search must have been configured in SOA Manager. For more information, see Configuring User-Defined Search in Messages.

User-Defined Selection

On the User-Defined Selection tab, you can specify up to five pairs of search names and values from the field help. The available search names correspond to those in the user-defined search configurations (they are not the names of the configurations themselves, but the search parameters specified within them).

Example: Search Name 1 = CustomerID, Search Value 1 = 123456.

You can specify whether you want to search for all of the search names and values (AND) or for at least one (OR). If you want to include the selection criteria from the Standard Selection tab, you can select the check box.

Advanced Selection

On the Advanced Selection tab, you can define more technical attributes for the message selection query. Note that entries in the Advanced Selection overrule the Standard Selection. Again, you can select messages using a set of identifiers for the asynchronous processing queue or the message persistence entry. In rare cases, a message ID can actually represent two messages, one at the service consumer side and one at the service provider side, which can both be stored on the same system. A message persistence ID, on the other hand, is a unique identifier for a message. You can also query messages based on a time range, and you can restrict your result set by specifying the SAP passport identifiers root context ID and transaction ID. The SAP passport can be used to identify communication entities in cross-system communication. It can be helpful to get an end-to-end monitoring view in a communication scenario where the message ID cannot be used as a unique ID throughout all systems involved.