Monitoring 

Any scenario based on usage type PI can be monitored using the SAP NetWeaver standard monitoring solution CCMS (Computing Center Management System).

Depending on the implementation basis (ABAP or Java technology) for the respective component, additional tools for detailed monitoring and for problem and performance analysis are available.

The Runtime Workbench (RWB) offers a central entry point for monitoring purposes. The following monitoring functions are supported:

●     Component monitoring

The RWB enables easy configuration of component monitoring instead of directly using CCMS for this purpose.

The RWB also offers a component-oriented monitoring that enables you to check and customize the runtime settings for the different components of usage type PI, for example. This also includes an “is-alive-check”.

●     Message monitoring

Message monitoring focuses on tracking the message processing status within a usage type PI component and on error detection and analysis.

●     End-to-end monitoring

End-to-end monitoring focuses on the monitoring of a message lifecycle from the usage type PI point of view. The RWB offers a user interface to configure the end-to-end message monitoring. For example, you can specify the components for which the trace should run and which trace level (degree of detail for the tracing) to use.

●     Performance monitoring

Statistics about different performance aspects of usage type PI can be accessed through the RWB. Here, you can select and aggregate performance data, for example, by component, time range, or message attributes.

The RWB provides performance monitoring specific to usage type PI. The RWB user interface offers several ways to create performance statistics. The main parameters are the message throughput and the latency.

For more information, see the SAP NetWeaver Process Integration Tuning Guide on SAP Service Marketplace at service.sap.com/instguidesNW04s → Operations → Process Integration.

●     Index administration

By administering and monitoring the indexing of messages per SAP XI component, you enable an index-based message search that you can use in message monitoring. This kind of message search offers you enhanced selection criteria including adapter-specific message attributes and terms or phrases from the message payload.

To be able to index messages, you require the search and classification engine TREX. See also Technical Operation of Search and Classification (TREX).

●     Alert configuration

By using the Alert Framework, central monitoring can be provided with all errors reported during message processing in ABAP and Java. This enables an improved reaction to such errors in both the ABAP runtime and the Java-based Adapter Engine. For this purpose, the Alert Framework is provided with rules based on certain events and on information from the header of the message protocol. These rules determine whether alerts are send or not. If an alert is sent, it can be used for error analysis.

●     Alert inbox

The alert inbox is user-specific and displays all the alerts for each alert server that have been generated based on the alert configuration.

●     Cache monitoring

Cache monitoring displays objects that are currently in the runtime cache. Different cache objects are monitored depending on the cache instance concerned.

For more information about the RWB, see Central Monitoring.