Monitor for Processed XML Messages 

Use

You can use the monitor for processed XML messages to display information about previously persisted XML messages that you select beforehand according to particular criteria.

You can display messages from the list individually and compare existing versions with each other.

Integration

To display information on XML messages, the messages must first have been logged. An XML message is logged when it is processed if:

·        It is an asynchronous message (persisted implicitly)

·        Logging for the underlying pipeline is activated (general logging of all pipeline steps or targeted logging of a particular pipeline step)

For each message there then exists the original message and any possible existing versions.

Versions of an original message only exist if message processing including logging was executed, or if the message was implicitly persisted following a particular pipeline step.

·        If logging is activated at pipeline level, a new version of the message is saved each time a pipeline service is called.

·        If logging is activated at pipeline element level, a new version of the message is saved following processing by the pipeline element concerned.

·        If logging is activated at pipeline service level, a new version of the message is saved when this pipeline service is called successfully.

In this way, changes to messages called by pipeline services can be monitored. Therefore, depending on the way that logging is configured (for pipeline, pipeline element or pipeline service), you either monitor all services or just critical ones.

Prerequisites

From the user menu Exchange Infrastructure, you chose: Monitoring ® Integration Engine – Monitoring and the system now displays the screen Integration Engine: Monitoring.

Activities

From the menu option Monitor for Processed XML Messages, you have three different ways of selecting processed XML messages. You can do the following:

·        Evaluate information for all processed XML messages

·        Search for XML messages with errors only

This enables you to quickly access all XML messages processed by the Integration Engine that have the status Error (). Using the list that the system then displays, you can restart XML messages with errors.

·        Identify XML messages with critical time delays

XML messages are normally processed immediately by the Integration Engine. If this is not the case, then you can select the XML messages that were delayed during processing.  The following rules apply here:

¡        Synchronous XML messages are selected if they were processed 60 seconds (or longer) after they were sent.

¡        Asynchronous XML messages are selected if they were processed 5 minutes (or longer) after they were sent.

In each of the three cases you also have the option of selecting acknowledgment messages as well. The system then displays a list of persisted XML messages.

If you do not have administrator authorization (S_XMB_ADM), the system only displays XML messages from the current client.