Monitoring
Any scenario based on SAP NetWeaver PI can be monitored using the SAP NetWeaver standard monitoring solutions CCMS (Computing Center Management System) and SAP NetWeaver Administrator.
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.
SAP NetWeaver Administrator offers an entry point for PI monitoring purposes. The following monitoring functions are supported:
SAP NetWeaver Administrator enables easy component-oriented system status monitoring instead of directly using CCMS for this purpose. It also includes availability and performance checks for the different components of usage type PI.
Message monitoring focuses on tracking the message processing status within a PI component and on error detection and analysis.
Statistics about different performance aspects specific to PI can be accessed here. You can select and aggregate performance data, for example, by component, time range, or message attributes.
The user interface offers several ways to create performance statistics. The main parameters are the message throughput and the latency.
More information: SAP NetWeaver Process Integration Tuning Guide on SAP Service Marketplace at service.sap.com/instguidesnw → SAP NetWeaver Process Integration 7.1 → Operations.
●
Communication channel
monitoring.
Used to monitor and administer the communication channels defined for a given Adapter Engine. It also provides runtime information about the communication channels of individual adapters, provided that these adapters are registered for this kind of monitoring.
Cache monitoring displays objects that are currently in the runtime cache. Different cache objects are monitored depending on the cache instance concerned.
By using the Alert Framework, PI 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.
In addition, SAP NetWeaver Administrator offers links to further tools, for example, for:
End-to-end
monitoring focuses on the monitoring of a message lifecycle from a PI point of
view. A user interface is offered 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.
The alert inbox is user-specific and displays all the alerts for each alert server that have been generated based on the alert configuration.
Used to monitor the status of the Java proxy runtime.
By administering and monitoring the indexing of messages per PI 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.
More
information:
Administration of
Search and Classification (TREX).
More information:
PI
Monitoring.
All of these monitoring functions can also be accessed with the Runtime Workbench.