Monitoring ABAP Web Service Messages

Selecting Messages

Start the message monitor from the Monitoring tab in SOA Manager (transaction code SOAMANAGER). You can also start the message monitor in SAP GUI using transaction code SRT_MONI. On the initial screen of the message monitor, you define the selection criteria of the messages you want to display in the message monitor.

1. Choose a result output:

   • Choose Detail (default selection) to display a list of all individual messages that match your search criteria.

   • Choose Summary to display a summary of the messages that match your search criteria.

2. Choose a view.

   • Choose Basic View to display only the most important attributes of the messages.

   • Choose Technical View to display an extended set of attributes of the messages as well as possible actions.

3. Choose the selection criteria you want to use. For more information, see Selection Criteria for Web Service Messages in the Message Monitor.

4. Execute the message query.

   The messages that match your selection criteria are displayed in the specified view, either as a summary or as a detailed list.

5. In the detailed result list, you can reselect messages by choosing Re-Select at the top of the list. This gives you similar selection options as the initial selection screen.

In the detailed list, the system displays a list of messages according to your selection criteria. If you have chosen to display a summary of the messages, the number of messages in this status is displayed for each processing status group. You can double-click a line to get the message list with details about each of these messages.

The message list is either displayed in basic view or technical view. The basic view displays a predefined set of message attributes. In the technical view, some more technical attributes, such as the unique message persistence ID, are shown. By default, the technical view does not show all possible attributes for a message, but you can define a personal view with the attributes you are interested in.

Working with the Message List

• For messages that you select in the list, you can display the following related messages:

  Sequence messages

  Displays all messages belonging to the same sequences as the selected messages as an extension of the current selection.

  Parent messages

  Displays all parent messages of the selected messages. For example, a parent/child relationship exists in an event scenario, where starting from an initial event message, multiple child messages can be created that have the initial event message as parent message.

  Child messages

  Displays all child messages of the currently selected messages.

• Exporting message data

  You can export a message list in different formats using the standard functions of table controls.

Messages from Mappings

A consumer proxy with asynchronous operations can either be defined to run within the application program context (in coupled mode) or later in a separate context (in decoupled mode, with an asynchronous border). The consumer mapping inherits this property from the consumer proxy implicitly and it is displayed in the message monitor.

In a coupled mapping, the source message is mapped to the target message without storing the source message. Only the message that is actually sent is stored. Therefore, the message is displayed as a normal message. However, in the Coupled column, you can still see that a message originates from a coupled mapping.

Messages that originate from decoupled mappings are displayed with adapter type Mapping. In a decoupled mapping, a message is created and saved, before the mapping takes place. After the mapping, the message is persisted again. The original message is stored with the adapter type Mapping, the target message is a normal message again. In the monitor, this source message is then displayed as a parent message of the target message.

Working with Individual Messages in the Message List

From the message list, you can carry out the following activities:

• Restarting messages

  You can restart messages that have an error status. The messages are added to the asynchronous processing queue to be processed again. For example, a restart like this can make sense if the configuration was changed after the last execution trial that produced the communication error.

  To restart more than one message at a time, use the SRT_UTIL_RESTART program. See Restarting and Canceling ABAP Web Service Messages.

• Restarting a message with debug

  If you only select a single message with an error, you can restart it and start the debugger in the Web service runtime code. Note that the debugger is not started in the application code.

• Displaying user-defined search values

  Choose Display UDS values to display the user-defined search values that were extracted from the selected messages.

• Canceling messages

  You can cancel messages that have an error status. Canceling a message sets it to the final status Cancelled without processing it. In some cases, a message cannot be canceled in the message list screen. It then needs to be canceled from the inconsistent message list screen.

  To cancel more than one message at a time, use the SRT_UTIL_CANCEL program. See Restarting and Canceling ABAP Web Service Messages.

• Consistency check

  The consistency check is only available in the technical view. It checks the consistency between the message status data and the asynchronous processing data. Note that the inconsistencies are only detected after a period of 5 minutes after the activity that led to the inconsistency.

  The consistency check produces the inconsistent message list. This list is similar to the general message list, but it shows some more technical detail information, because it is intended for support activities. In the inconsistent message list, you cannot do a general reselection, but you can run a consistency recheck for the displayed messages. You can also enforce the cancelation of selected messages. In this case, the system skips some checks that are carried out if you cancel messages in the general message list.

• Displaying details of a message

  From the message list and from the inconsistent message list, you can display details for a single message by clicking on the message ID. By default, the payload view is displayed with all message details. A table shows the message payloads. If there was an error, the initial message version and the error versions are available. You can display an XML view of the payload by choosing Original XML in the upper menu. To display more details, such as header information and the message structure, you can change the view of the message detail screen. For example, you can then see if a payload is stored as an attachment to the actual message.

• Monitoring Sequences

  You can navigate to the sequence monitor from the message list or directly using transaction code SRT_MONIS. For more information, see Monitoring Sequences.