BPE Monitoring

Posted on May 14, 2010 at 09.27 AM - Kuala Lumpur, Malaysia

It's never easy to monitor workflow, further more to monitor BPM. The most useful transaction for monitoring purpose would be SXMB_MONI_BPE.

1. The first 3 reports is just for us to display our process instances based on certain search criteria. It's good idea to populate field 'Component' with the integration process name, as to narrow down the search.
2. The 4th report is used to display process instances which are already has the missed deadline.
3. The 5th report is used to display process instances which ended with errors.
4. The 6th report is used to display messages which ended up with error in the queue. You can check which queue the messages went through using normal integration engine monitor SXI_MONITOR.
5. The 7th report is used to rerun the process instance after some temporary error. One typical example would be when the document is being maintained by the user, when PI is trying to update the document which will end up with error.
6. The 8th report is used to rerun the process instance after system crash. One typical usage would be when the power source is cut off and the server went down which cause the process instance 'hang' in the system.

You can check further for any errors to the messages using:

1. SM58 to display transactional RFC which are still in the queue
2. SMQ1 to display outbound queue content
3. SMQ2 to display inbound queue content
4. SMQS to display status of outbound queue
5. SMQR to display status of inbound queues

Other PI monitoring which are popular is SXMB_MONI which consist multiple tools just like SXMB_MONI_BPE.

1. The first report is the most commonly used report to display messages passing by integration server
2. The 2nd and 3rd reports are used to display archived XML messages
3. The 4th report is to display archiving and delete jobs
4. The 5th report is used to display analysis on the persistence layer which stores BPM data when it's not loaded in the memory
5. The 6th report is used monitpr synchronous and Asynchronous communication

You can also check correlations which are still active using report RSWF_CRL_MAINTAIN

It's also possible for you to stop business process engine (BPE) if needed using transaction SWF_XI_ADM_BPE

Life is beautiful! Let's make it meaningful and colorful!