Transaction code SXMB_MONI is used to monitor the processing of XML messages, as well as to track message errors and statutes. Message throughput can also be monitored. Monitoring initially helps the system administrator to monitor their system and at the same time it is used by the application as a processing monitor.
To call a menu option with an execute icon, double-click it. Alternatively, position the cursor on the line in question and choose Execute Function.
Monitor for Processed XML Messages
Use this function to determine all XML messages processed by the Integration Engine according to the following selection criteria:
- Date Sent or Date Executed or both
- Sender/Receiver Definition
- Logical pipeline ID
- Technical inbound channel/technical outbound channel
- Message ID
- Error Code
- Client / User
By selecting a message status or condition or both you can restrict the selection further still. In each case the system then displays a list of all XML messages, sorted according to the time and date they were processed, that satisfy the given selection criteria. From the list you can directly display the individual XML messages and go to their versions.
Archived XML Messages (Search Using Archive)
All XML messages processed by the Integration Engine that have already been archived can be displayed from the archive.
On execution, this function first gives you a list of all available archive files.
When you select an archive, a list of all XML messages stored in this archive is generated, sorted according to the time and date they were processed. From the list you can directly display the individually archived XML message or you can go to a version comparison.
Archived XML Messages (Search Using ID)
All XML messages processed by the Integration Engine that have already been archived can be displayed from the archive. If you execute this function, you will first be shown a list of all archived messages.
Select a message ID to display that particular archived XML message or to go to a version comparison.
Job Overview
The job overview provides an overview of all background jobs that access the persistence layer of the Integration Engine.The persistence layer contains all processed XML messages until they are deleted and therefore enables them to be logged continuously.
The job overview is divided into two parts:
- All active jobs with the time stamp from the start of the job
- All processed jobs with the time stamp from the end of the job
The following background jobs access the persistence layer:
- Job to select XML messages to be deleted (SAP_BC_XMB_PRE_DELETE_[client])
- Job to delete selected XML messages (SAP_BC_XMB_DELETE_
[client]) - Job to select XML messages to be archived (SAP_BC_XMB_PRE*)
- Job to archive selected XML messages (SAP_BC_XMB_WRI*)
- Job to delete archived XML messages from the persistence layer (ARV_BC_XMB_DEL*)
- Job to copy XML messages not to be deleted, from the active to the inactive database tables of the persistence layer, followed by activation of the inactive tables. This is not a job in itself, since this action is the second step in a deletion job.
- Job to extract application data from the header of XML messages and save it in the application container tables (SXMB_APPL_MONI_COLLECT)
Persistence Layer Analysis
This function provides you with an overview of the current status of the persistence layer.
The persistence layer contains all processed XML messages until they are deleted. Due to the volume of data to be processed, it is a critical part of the Integration Engine. For this reason it is vital that the user has quick access to information about the status of the persistence layer.
The analysis contains information about the number of XML messages currently in the active data container. It also displays the maximum possible number of XML messages. This data is used to determine the fill level of the tables.
