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 .
Adapter Engine status monitoring
Used to display current technical data of the selected Adapter Engine across several server nodes.
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.
Used to monitor the status of the Java proxy runtime.
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.