03 Message Monitoring

8/18/2019 03 Message Monitoring

1/19

1

Message Monitoring& Message Monitor ing Examples

Andrea Schmieden


2/19

2

© SAP AG 2004, BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting /Message Monitoring & Message Monitoring Examples

Agenda

Business Process Engine Overview

Runtime CacheProcess Execution Monitoring

Message Monitoring

Message Monitoring Examples

Event Trace

Troubleshooting


3/19


4/19

4

Using transaction SXMB_MONI you can find message invoking an integrationprocess by checking the inbound and outbound values.

PE (Process Engine) indicates that an integration process is involved.


Message Monitoring – Integration Process

PE (ProcessEngine) indicates

Integration Processis involved


5/19

5

You use the monitor for synchronous/asynchronous communication to display status information about persistedmessages where a coupling of synchronous and asynchronous processing has occurred.

The status monitor for synchronous/asynchronous communication provides the following information as thedefault:

The number of active synchronous calls that are still waiting for a response

The number of canceled processes (synchronous calls) whose status has not yet been deleted

A table containing status information about the involved synchronous request messages

The system displays the following status information:

The exception with a green, yellow, or red status

The colors of the status have the following meanings:

Green: The call is still waiting.

Yellow: The pipeline timeout has been exceeded but the call has not yet been canceled.

Red: An error has occurred and the call has been canceled.

The message ID of the synchronous request

The date and time of the transfer of the request to the Business Process Engine

The time of the timeout of the Integration Engine pipeline

The status of the Integration Engine pipeline

The technical name of the application server

The status of the Business Process Engine

The current settings of the involved configuration parameters.

Acti viti es

In the status monitor for synchronous/asynchronous communication, you can execute the following activities:

Close all canceled processes.

Update the entire display by choosing Update in the application function bar.Update the table of displayed messages by choosing Update in the table symbol bar.

Navigate from the list of displayed messages to the corresponding workflow log. To do this, click the messageID of the respective message.


Status Monitor for Sync/Async Communication

Transaction Code: SXMS_SAMON


6/19

6


Agenda

Business Process Engine Overview

Runtime CacheProcess Execution Monitoring

Message Monitoring

Message Monitoring Examples

Event Trace

Troubleshooting


7/19

7


Message Monitoring Example Overview

ScenarioBusiness sys tem Travel_Agency_PL sends message to integration

process SplitFlights_ProcessPLThe integration process spli ts the message and sends five newmessages to business system ReservationSystem_PL

MonitoringDisplay relevant messages

Display workflow log with details for each step

Display work item con tainer with message

Compare messages before / after spli t


8/19

8

Open two SAPGui windows with SXMB_MONI:

Messages sent from Travel_Agency_PL to SplitFlights_ProcessPL.

Messages for PE service SplitFlights_ProcessPL


Display Relevant Messages (1)

To display m essagessent from

Travel_Agency_PL toSplitFlights_ProcessPL

To display messages forPE service

SplitFlights_ProcessPL


9/19

9


Display Relevant Messages (2)

SXMB_MONI disp laysmessage to be analyzed


10/19

10


Display Workflow Log (1)

1. Click PE

2. Click Icon


11/19

11



Click List WithTechnical Details


12/19

12

Workflow log displays complete process with all steps (work items).

To display the container and the XML message used in this process step / workitem, click Show Work item Container.



Click Show WorkItem Container


13/19

13

To display the message before transformation, select the Table icon precedingMESSAGES_IN. The table is displayed in the lower right window pane. From thecontext menu select Nested Table -> MESSAGES.

To display the message after split, select MESSAGES_OUT and perform thesame steps as for MESSAGE_IN.


Display Work Item Container

To display themessage beforetransformation

Click Table icon ofMESSAGES_IN


14/19

14

Open context menu for value 1 and select Nested Table -> Messages.

Open context menu for Instance ID and select Default method


Display Message Before Split (1)


15/19

15

XML message before split


Display Message Before Split – (2)

Doubleclick


16/19

16

Open context menu for 1 and select

In this case five new messages were created


Display Messages After Split (1)


17/19

17


Display Messages After Split (2)


18/19

18

This new message is sent from Process Engine (SplitFlights_ProcessPL process)to IS pipeline.


Check XML Message (1)

Navigate tocreated XMLmessage byclicking the

GUID


19/19

In the container view you can also use the context menu (right click) using thedefault method to check the XML message.


Check XML Message (2)

03 Message Monitoring

Documents

Transcript of 03 Message Monitoring