Active XMB Monitoring

You monitor XMB Messages for specific errors by creating a set of registry entries; if an XMB Message reports a specified error, the corresponding event will be raised. The raiser comment of the event contains specific XMB Message information such as the DocId and MessageId.

You specify the registry entries for XMB Message Monitoring as follows:

/configuration/sap/<sap_system>/xmb/monitoring/Message/<message_type>=<options>/Event/<event>

Where

• <sap_system> is the name of your SAP system, such as PR1 for example
• <message_type> is the message type of the XMB Message, such as MSG1 for example
• <options> comma-separated key=value pairs of options to match the XMB message
• <event> is the name of your Redwood Server event to raise

The key part of the <options> can be any field in the SAP structure SXI_MESSAGE_DATA_LIST

You specify the XMB Message statuses in the Value field of the <event> registry entry; multiple values are specified comma-separated. The Event registry entry can have more than one <event> child key.

The raiser comment contains the following information:

XMB: Message GUID/state/type/queue/sending_system/receiving_system

Example

You specified the following two registry entries:

/configuration/sap/CPI/xmb/monitoring/Message/MSG1
ADAPT_TYP=IDOC

/configuration/sap/CPI/xmb/monitoring/Message/MSG1/Event/XMBEvent
05, 06, 21

The XMB Message E9DCD997B75B49E40ADDB0EC5ECE0132 reached status 06, which matches the value of the registry entry. The event XMBEvent is raised with the following raiser comment:

XMB: E9DCD997B75B49E40ADDB0EC5ECE0132/06/A/XBTO1___0001/In/I46_200

Prerequisites

• ProcessServerService.SAP.XMBMessageMonitoring license key set to true