The Middleware Trace Monitor 

Use

The Middleware Trace Monitor is a tool to record events and display the recorded information.

Integration

As this trace function is the standard Trace Monitor on the CRM Server, additional or redundant information is not saved anywhere else, such as in the R/3 backend system or application log.

Prerequisites

To use the Middleware Trace Monitor you have to make the relevant settings. Choose Architecture and Technology ® Middleware ® Monitoring ® Message Flow ® Setup Middleware Trace.

Example of Trace Settings in a Parameter Table:

Column	Setting
Environment	F_ Message Flow
Component
Trace Object ID
Trace Level	1 Warning

For details on the parameters refer to Trace Levels and Trace environments.

Features

The Middleware Trace Monitor consists of four parts:

·        An application programming interface to write and save information

·        A User Interface to display the saved information

·        An export tool to export and save data in simple text files (for example, for customers)

·        A reorganization tool to clean-up the database

The recorded data is first stored in the trace buffer within the global memory area. With certain events, for example, if there is an error, there is an automatic buffer flush, and the content of this buffer is written to the database.

Activities

For details on how to call the Trace Monitor refer to Calling the Trace Monitor.

There are two groups of trace data:

·        Errors and warnings

·        Messages or error characters with additional information

Depending on the data you want to display, you can specify different trace levels

To get a higher granularity of the trace data, you can also choose between several trace environments.

Trace Levels

You can use different trace levels:

·        Level 0: Error

Only difficult errors should be reported, for example, Tablespace full.

·        Level 1: Warning

Only circumstances that could lead to an error if the system is operated further should be reported. For example, High watermark reached, operator intervention is required.

Level 1 is the standard setting in production systems. So, the default is that only errors and situations requiring operator intervention are reported.

·        Level 2: Service Flow:

The services running in Middleware are recorded. This data is saved automatically.

·        Level 3: Detail info1:

No critical warnings. Only additional information on the executed programs and modules. This level should only be used by developers.

·        Level 4: Detail info2:

Program-specific information Only for developers, for example, to search for errors.

Trace Environments

You can use the available trace environments to run a trace with different levels. For example, you could perform a delta download in the environment “D” with trace level 4, while the “normal“ flow runs with standard level 0 or 1 in trace environment “F”.

The following environments are available:

Environment	Use
'  '	Standard environment
D	Delta data synchronization
F	Flow environment
R	Replication
G	Generation
I	Initial Load
T	Test environment
X	Internal trace environment