Monitoring
Monitoring is divided into the following areas:
● General monitoring functions
● Monitoring the mobile devices
● Monitoring Smart Synchronization
Various monitoring applications and log applications are provided for these areas. The applications check and monitor the mobile devices and Smart Synchronization in the background and supply information about the status of these two areas. Consequently, they can help to identify critical system events.
Since the Mobile Infrastructure (MI) usage type is installed together with the usage types Application Server ABAP (AS ABAP) and Application Server Java (AS Java), it is important to refer to the information contained in the sections AS ABAP - Monitoring and AS Java - Monitoring.
The following monitoring functions are provided:
Function |
Description |
Call |
General monitoring functions |
||
Monitoring
synchronization |
The following monitors are available to monitor synchronization: ●
●
●
●
|
SAP NetWeaver
Administrator: ● Generic Sync Queue Monitor ● Technical Sync Monitor ● Smart Synchronization Replication Monitor ● SyncBO Processing Statistics |
Monitoring the mobile devices |
||
MI is connected to
the monitoring architecture of the CCMS (Computing Center Management System).
The concept of this monitoring architecture is to provide all the required
information (for example, availability, configuration data, log and trace
files) in a single, central monitoring system. As soon as problems occur, they
are displayed in the alert monitor. Special MI tools that support working with the CCMS: ●
Alert monitor ●
Reorganization
tool |
CCMS: SAP NetWeaver
Administrator: MI Server: Reorganization tool:
|
|
Status overview
for mobile components |
You can track the
current status of a mobile component on a particular mobile device in the
|
SAP NetWeaver
Administrator: |
Tracing(
|
The trace function is available for the SAP MI Client Component and is already activated by default. The trace files accumulates information over a long period of time. Different trace levels are available. The trace files applog.txt and trace.txt are written to the <MI_HOME>/log directory. |
CCMS: Log
Viewer: |
Performance
tracing |
If problems occur with the system performance, you can register all the relevant activities on the mobile device and then send the log file to the server to be evaluated. Refer to SAP Note 851831 for further information. |
Log Viewer: Display and analysis of data (trace format) |
Configuring Log Severity Levels |
To denote the level of importance or relevance of a certain log, you can configure the SAP MI log severity levels in the Log Configuration in the SAP NetWeaver Administrator.. |
SAP NetWeaver
Administrator: From the Show dropdown box, select Logging Categories. Category: /applications/MI Monitors. The default severity value is INFO. |
Configuring Tracing Severity Levels |
To denote the level of importance or relevance of a certain trace, you can configure the SAP MI tracing severity levels in the Log Configuration in the SAP NetWeaver Administrator.. |
SAP NetWeaver
Administrator: From the Show dropdown box, select Tracing Locations. Location: com.sap.ip.mi. |
Monitoring Smart Synchronization |
||
Synchronization
overview |
In the
You use the monitoring tool if you want to check the processing of particular worklist items, for example. |
MI server: |
Synchronization
message display |
You can view the details about synchronization messages from the inbox or outbox. |
MI Server: |
Logging |
You can use the log tool to find errors that occurred in Smart Synchronization. To optimize performance and system resources, you can configure different log levels. You use the log tool, for example, if you want to check worklist item-independent processes (for example, the replicator). |
MI server: |