You are on page 1of 14

Process Execution Monitoring

Andrea Schmieden

1

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 / Process Execution Monitoring 2 .

BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Process Execution Monitoring „ There are many transaction codes you can use to monitor workflow executions.SXWF_XI_SWI6 z Diagnosis Processes with Errors .SXWF_XI_SWI2_DIAG z Continue Processes Following Errors – SXWF_XI_SXPR 3 . The workflow log enables you to see exactly what is happening in the workflow. The exercise that accompanies this unit includes a detailed look at several of the monitoring functions. „ In this lesson we will focus on the monitoring transactions highlighted above: z Process Selection – SXWF_XI_SWI1 z Processes for One Message Type – SXWF_XI_SWI14 z Processes for a Message .Monitoring Workflow Execution SXWF_XI_SWI1 SXWF_XI_SWI14 SXWF_XI_SWI6 SXWF_XI_SWI2_DIAG SXWF_XI_SXPR Transaction code: SXMB_MONI_BPE © SAP AG 2004. „ Almost all monitoring transaction codes take you to the workflow log. The entry point for the monitoring workflow is transaction code SXMB_MONI_BPE.

4 . You could look at only executions in COMPLETED status. The primary difference is the selection criteria used to get to the workflow log. STARTED status. „ You also may need to change the date/time range to get the executions that interest you. This is normally easier than looking at each step individually. you will look at the log for each workflow. CANCELLED status. „ By designating F as the type of work item.Process Selection – Select which workflows © SAP AG 2004. „ You could also change the Status field. ERROR status. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Process Execution Monitoring „ All the reports lead to the same workflow log.

just double-click on any entry. „ Notice here you can also see the workflow number (WS#######). To get more details on any execution.Process Selection – Pick the Exact Workflow © SAP AG 2004. 5 . BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Process Execution Monitoring „ Now you see a list of all workflows that have executed. and the status of the workflow.

when it was executed. „ In the example above everything is completed. 6 . View: Workflow Agents. „ If you click on the Graphic column you can see the same workflow log displayed graphically. „ There are three tabs: View: Workflow Chronicle.Process Selection – Completed Workflow Status Legend: Workflow Step © SAP AG 2004. „ The icon with the circular shape represents a workflow (WS). View:Workflow Objects. The icons next to steps such as ‘Mapping’ and ‘Send Message Asynchronously’ represent steps in the workflow. „ If you click on the Details column you can find out information such as who executed the work item.”. This log is for “Simple_Mapping_Pipe…. „ If you select the third tab. This is the exact name of the Integration (Business) Process created in the Integration Repository. View: Workflow Objects. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Process Execution Monitoring „ Now you can see the actual workflow log. you can see the message GUID for this workflow.

BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Process Execution Monitoring „ Here is the log for another workflow. 7 . To get more details you need to drill into the technical view of the log. This workflow is for Integration (Business) Process SO_EVENT_RESOLUTION… „ This workflow is ‘In process’.Process Selection – In Process Workflow Status Go to the technical log © SAP AG 2004. You cannot research or solve many problems in this non-technical view of the log. Some steps in the workflow are completed. „ This view of the log is a non-technical view of the log. but notice the last step is ‘In Process’.

„ In the graphic above. the status is Ready. the status is In Process. If the box is not filled. but no action has started on this step. You no longer want this execution of the workflow. 8 . The Ready status means the step is ready for work to happen on the step. the status is Completed. „ In this view the boxes represent the status of each step. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Process Execution Monitoring „ This is the technical view of the log. the last step is in ready status. „ NOTE: You should do considerable research before deciding to cancel a workflow execution. Also notice this is step number 45. if a box is completed filled in. „ To do this you can click on the last line where you see step number 45 – atp. Perhaps you just want to cancel this execution. Under the Status column. If the box is partially filled in.Process Selection – Technical Log Click here to research further Legend: Completed In Process Error Ready © SAP AG 2004. The exercise in this unit walks you through reading this log. „ Let us assume you have researched this and you need to manually set this workflow to complete.

A “Wait Step” means the workflow is waiting for something to happen. In this situation you might have to Logically Delete. „ Depending on the status and type of type. (Perhaps waiting on a message confirmation. You can also Logically Delete the workflow which will also stop the execution. „ At this point you have various options of what you can do with this workflow execution. sometimes Complete Manually will work. then selecting Edit -> Change.Process Selection – Workflow Cancellation Options for changing a workflow execution © SAP AG 2004. and sometimes it will not. „ Normally you should not manually complete or cancel workflow executions. You can Complete Manually to end the workflow. Logically delete will end the execution and set the status of the workflow to CANCELLED.) „ Oftentimes Complete Manually does not work with a “Wait Step”. 9 . In this particular case we have a “Wait Step”. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Process Execution Monitoring „ The graphic above is the screen you receive after clicking on a step in the workflow log.

„ In this transaction code. SXWF_XI_SWI14. The difference is how to search for a workflow execution. „ Now you will receive the logs only for a particular Interface Name or Interface Namespace. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Process Execution Monitoring „ All other monitoring transactions take you to the same workflow log. 10 .Processes for One Message Type Transaction Code: SXWF_XI_SWI14 © SAP AG 2004. you can search by a specific Interface Name or Interface Namespace.

„ For example. here you can get the log for an exact GUID. 11 . you have the GUID number for a particular message and you want to see all workflow executions tied to that GUID. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Process Execution Monitoring „ In transaction code you can get the workflow log for a particular message GUID. „ If you have a interface that executes thousands of times a day.Processes for a Message Transaction Code: SXWF_XI_SWI6 © SAP AG 2004.

it starts from the point of the error. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Process Execution Monitoring „ In this transaction code you receive all workflows with errors. „ For each work item you can double-click to research the error.Diagnosis Processes with Errors Transaction Code: SXWF_XI_SWI2_DIAG © SAP AG 2004. You can highlight any of them and select Restart Workflow. 12 . If you choose to restart the workflow.

You could use this transaction code if every workflow failed for the last 2 minutes and you want to restart all of them. BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Process Execution Monitoring „ This transaction code is another way to do a restart. 13 . „ You could also use this transaction code to look at workflows in error and restart particular ones. Here you can restart many in mass by selecting Restart immediately.Continue Processes Following Errors Transaction Code: SXWF_XI_SXPR © SAP AG 2004.

„ The Queue ID column will list the workflow that was executed for this message.Workflows from Message Log © SAP AG 2004. you can see which ones are execute workflows. 14 . BPM@BSGs / Andrea Schmieden / Monitoring & Troubleshooting / Process Execution Monitoring „ If you are looking at the XML messages. „ You could take the Message ID for a particular workflow. go to transaction code SXWF_XI_SWI6 (Processes for a Message) and find all specific workflow executions for this Message ID (GUID).