You are on page 1of 19

Message Monitoring

& Message Monitoring Examples
Andrea Schmieden

1

BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Message Monitoring & Message Monitoring Examples 2 .Agenda „ Business Process Engine Overview „ Runtime Cache „ Process Execution Monitoring „ Message Monitoring „ Message Monitoring Examples „ Event Trace „ Troubleshooting © SAP AG 2004.

Message Monitoring Display messages processed by the Business Process Engine Transaction Code: SXMB_MONI © SAP AG 2004. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Message Monitoring & Message Monitoring Examples 3 .

Message Monitoring – Integration Process PE (Process Engine) indicates Integration Process is involved © SAP AG 2004. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Message Monitoring & Message Monitoring Examples „ Using transaction SXMB_MONI you can find message invoking an integration process by checking the inbound and outbound values. „ PE (Process Engine) indicates that an integration process is involved. 4 .

‹Navigate from the list of displayed messages to the corresponding workflow log. ‹Update the entire display by choosing Update in the application function bar. click the message ID of the respective message.Status Monitor for Sync/Async Communication Transaction Code: SXMS_SAMON © SAP AG 2004. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Message Monitoring & Message Monitoring Examples „ You use the monitor for synchronous/asynchronous communication to display status information about persisted messages where a coupling of synchronous and asynchronous processing has occurred. ‹The status monitor for synchronous/asynchronous communication provides the following information as the default: ‹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. 5 . or red status ‹The colors of the status have the following meanings: z Green: The call is still waiting. To do this. „ Activities „ In the status monitor for synchronous/asynchronous communication. z Red: An error has occurred and the call has been canceled. ‹Update the table of displayed messages by choosing Update in the table symbol bar. ‹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. yellow. z Yellow: The pipeline timeout has been exceeded but the call has not yet been canceled. you can execute the following activities: ‹Close all canceled processes.

Agenda „ Business Process Engine Overview „ Runtime Cache „ Process Execution Monitoring „ Message Monitoring „ Message Monitoring Examples „ Event Trace „ Troubleshooting © SAP AG 2004. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Message Monitoring & Message Monitoring Examples 6 .

BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Message Monitoring & Message Monitoring Examples 7 .Message Monitoring Example Overview „ Scenario „ Business system Travel_Agency_PL sends message to integration process SplitFlights_ProcessPL „ The integration process splits the message and sends five new messages to business system ReservationSystem_PL „ Monitoring „ Display relevant messages „ Display workflow log with details for each step „ Display work item container with message „ Compare messages before / after split © SAP AG 2004.

BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Message Monitoring & Message Monitoring Examples „ Open two SAPGui windows with SXMB_MONI: ‹Messages sent from Travel_Agency_PL to SplitFlights_ProcessPL. ‹Messages for PE service SplitFlights_ProcessPL 8 .Display Relevant Messages (1) To display messages for PE service SplitFlights_ProcessPL To display messages sent from Travel_Agency_PL to SplitFlights_ProcessPL © SAP AG 2004.

Display Relevant Messages (2) SXMB_MONI displays message to be analyzed © SAP AG 2004. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Message Monitoring & Message Monitoring Examples 9 .

Click Icon 1.Display Workflow Log (1) 2. Click PE © SAP AG 2004. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Message Monitoring & Message Monitoring Examples 10 .

BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Message Monitoring & Message Monitoring Examples 11 .Display Workflow Log (2) Click List With Technical Details © SAP AG 2004.

click Show Work item Container. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Message Monitoring & Message Monitoring Examples „ Workflow log displays complete process with all steps (work items).Display Workflow Log (3) Click Show Work Item Container © SAP AG 2004. 12 . „ To display the container and the XML message used in this process step / work item.

select MESSAGES_OUT and perform the same steps as for MESSAGE_IN. 13 . BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Message Monitoring & Message Monitoring Examples „ To display the message before transformation. From the context menu select Nested Table -> MESSAGES. The table is displayed in the lower right window pane. select the Table icon preceding MESSAGES_IN. „ To display the message after split.Display Work Item Container Click Table icon of MESSAGES_IN To display the message before transformation © SAP AG 2004.

„ Open context menu for Instance ID and select Default method 14 . BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Message Monitoring & Message Monitoring Examples „ Open context menu for value 1 and select Nested Table -> Messages.Display Message Before Split (1) © SAP AG 2004.

BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Message Monitoring & Message Monitoring Examples „ XML message before split 15 .Display Message Before Split – (2) Double click © SAP AG 2004.

BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Message Monitoring & Message Monitoring Examples „ Open context menu for 1 and select „ In this case five new messages were created 16 .Display Messages After Split (1) © SAP AG 2004.

BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Message Monitoring & Message Monitoring Examples 17 .Display Messages After Split (2) © SAP AG 2004.

18 . BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Message Monitoring & Message Monitoring Examples „ This new message is sent from Process Engine (SplitFlights_ProcessPL process) to IS pipeline.Check XML Message (1) Navigate to created XML message by clicking the GUID © SAP AG 2004.

Check XML Message (2) © SAP AG 2004. 19 . BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Message Monitoring & Message Monitoring Examples „ In the container view you can also use the context menu (right click) using the default method to check the XML message.