The aim of monitoring the processing of messages packages in the BPE is to use the data collected to take error handling measures and to optimize message packaging configuration at process level.
More information: Activating and Configuring Message Packaging
To monitor message packaging at runtime, certain values are monitored and CCMS alerts are triggered when certain error situations occur:
● Heartbeat monitoring for the packaging job that triggers an alert if this job is no longer running regularly.
● Heartbeat monitoring for the reorganization job that triggers an alert if this job is no longer running regularly.
The following two monitors are available in CCMS for Process Integration under Business Process Engine → Runtime → Message dispatching:
● Dispatcher items in status ERROR
● Dispatcher items in status CANCELLED
More information: CCMS-Alert-Monitor
1. Start inbound processing monitoring with transaction SWF_INB_MON or SWF_INB_ADM.
Note that you require administrator authorization for transaction SWF_INB_ADM.
2. You can monitor the throughput of the inbound processing either on the basis of individual process system or system-wide. In this way you can display the throughput figures in any discrete time range, right down to seconds. A similar display for message packages allows you to monitor inbound processing with the same detail.
3. You can display runtime information about individual messages, for example, the total runtime of a message in inbound processing or just the runtime of a specific section of the inbound processing.
There are various functions in the BPE administration that can be used for troubleshooting. You need authorization for transaction SWF_INB_ADM to be able to use these functions.
4. Start the administration of the inbound processing (transaction SWF_INB_ADM).
5. Display messages that have not been processed, or have been processed incorrectly.
6. Depending on the message status in BPE inbound processing and its Quality of Service (QoS), use one of the following functions:
○ <Message> Reschedule – With this function you can resend the affected message to inbound processing. The message is treated as if it had just been sent from the adapter.
○ <Message> Logically Delete – With this function you can stop the messages affected from being transferred to inbound processing and from being processed. The message status is also set to canceled manually.
○ <Message> Lock – With this function you can temporarily take a message that has caused an error out of processing. As long as a message has this status, it is not processed by inbound processing and is temporarily not sent to inbound processing. It can be scheduled again later.
A message with errors with QoS Exactly Once (EO) is not processed until it is rescheduled. Other messages with QoS EO can be processed in the meantime, however. This means that if message packaging is active, other EO messages will not be held up by the EO message with errors. A message with errors with QoS Exactly Once In Order (EOIO) on the other hand will hold up subsequent messages until it is rescheduled.