eG Monitoring
 

Measures reported by SapB1MsgLogTest

The integration framework for SAP Business One is a Web browser- based solution to design integration flows for exchanging data between different systems. The integration framework provides an infrastructure that allows for the communication and interaction between software applications such as SAP Business One, other SAP solutions as well as non-SAP systems; whether they are cloud applications or on-premise applications. The purpose of the integration framework is to provide data mapping and transformed information to the software applications involved. The integration framework for SAP Business One supports various log types to analyze and troubleshoot the daily transactions generated by your integration scenarios.

The Message Log shows all messages being processed through the integration framework and allows you to view and debug the message through various processing steps. The information recorded in the log includes scenario package and step, sender and receiver system, trigger, date and time. The integration framework always processes data internally as XML messages irrespective of the inbound data format. The Message Log will capture the full XML message only when the Log Level parameter is set to “Full message“. The logs in the message log will be stored for a maximum of one day only. The logs will be lost if the SAP Business One is rebooted.

If the message log is not scanned periodically for messages with failure status, then, critical errors encountered in the integration framework may sometimes be overlooked by the administrators. If the issues / errors are not resolved on time, then, the integration framework may fail abruptly. To avoid such failures, it is essential to monitor the message log from time to time and periodically analyze the count of log messages based on their severity. The SapB1MsgLogTest helps administrators perform such diligent tasks.

This test scans the message log for messages and reports the count of messages that were recorded with Success, Failure, Processing and Filtered status. Using this test, administrators can figure out the severity with which maximum number of messages were recorded. This way, administrators can isolate messages with Failure status and can analyze the reason behind such frequent failures.

Outputs of the test: One set of results for the target SAP Business One being monitored.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Success_Messages Indicates the number of messages that were recorded with a Success status in the message log during the last measurement period. Number

A high value is desired for this measure.

Failure_Messages Indicates the number of messages that were recorded with a Failure status in the message log during the last measurement period. Number

Ideally, the value of this measure should be 0.

For each message that was recorded with Failure status, the detailed diagnosis of this measure lists the ID, Start time, Finish time, System ID of the Sender, System ID of the Receiver, Trigger, Result, Scenario Step and Scenario Package.

Processing_Messages Indicates the number of messages that were recorded with a Processing status in the message log during the last measurement period. Number

 

Filtered_Messages Indicates the number of messages that were recorded with a Filtered status in the message log during the last measurement period. Number

 

Processing_Rate Indicates the number of messages that were recorded with the Processing status per minute in the message log during the last measurement period. Messages/min

 

Failure_Rate Indicates the number of messages that were recorded with the Failure status per minute in the message log during the last measurement period. Messages/min