PI Monitoring Using the SAP NetWeaver Administrator

Caution Caution

SAP NetWeaver Administrator for PI and all monitoring tools it includes are not supported for use in production scenarios. We recommend to use Runtime Workbench for PI monitoring in production scenarios. The information provided below is only for reference.

For more information, see SAP notes 1446507 and 1247043.

End of the caution.

The central tool for monitoring the integration processes in your landscape is the PI Monitoring dashboard in Technical Monitoring Work Center in SAP Solution Manager. When you find there that certain processes or messages on a particular engine should be reviewed more thoroughly, you can navigate to the corresponding monitor in SAP NetWeaver Administrator.

Prerequisites

To be able to use the SAP NetWeaver Administrator for PI, you must first perform the following steps:
- Install CCMSPING and register the system that your SAP NetWeaver Administrator is to run on.
- Configure your SAP NetWeaver Administrator.
  More information: Configuring NWA for Landscape-wide Monitoring and Administration.
- If an Integration Server in your system landscape uses a different System Landscape Directory (SLD) to your SAP NetWeaver Administrator for PI, export the contents of the SLD for this Integration Server and import it to the SLD of SAP NetWeaver Administrator.
- You must add all the ABAP and Java systems that you want to monitor with your SAP NetWeaver Administrator.
  To monitor the Integration Server, you require the following systems:
  - The corresponding ABAP system with the client that is configured as the central Integration Engine.
  - The Java system that acts as the central Advanced Adapter Engine.
    You must also add all other advanced Adapter Engines and business systems with an Integration Engine that are to be monitored.
    
    More information: Adding a Monitored System to the NetWeaver Administrator.
To be able to use the SAP NetWeaver Administrator for PI, you require the following authorizations:
ABAP users must have one of the following roles:
- SAP_NWA_FULL
  Composite role with all authorizations
- SAP_NWA_READONLY
  Composite role with read-only access and corresponding restricted authorizations.
Java users must have one of the following UME roles:
- NWA_SUPERADMIN
  Role with all authorizations
- NWA_READONLY
  Role with read-only access and corresponding restricted authorizations
The ABAP roles are automatically assigned to the Java roles.

Depending on the role assigned to the user, particular elements on the user interface are either activated or deactivated so that only authorized users can perform the corresponding activities.

Features

Start SAP NetWeaver Administrator for PI from your PI start page (http://<host>:<port>/dir) under Configuration and Monitoring NetWeaver Administrator .

Displays an overview of the domains in your PI landscape with all the components involved.

More information: Monitoring PI Components.
Depending on the component, you can perform the following additional activities; however, not all tasks listed are available for all components:
With the exception of with message monitoring, it makes no difference whether you first select one of the activities and then the component, or reversed. You can also execute parts of message monitoring across different components.
- Monitoring Messages
- Monitoring Performance
- End-to-End Monitoring
- Alert Inbox
- Displaying Technical Data for the Adapter Engine
- Monitoring Communication Channels
- Monitoring Java Proxy Runtime
- Monitoring the Cache
- Prioritizing the Processing of Messages
  
  Note
  
  Some of these activities are integrated directly into the SAP NetWeaver Administrator, whilst some of them open functions on the Runtime Workbench.
  
  End of the note.
The following functions are provided for configuring and monitoring Web services:
- The Web Services Log Viewer for Viewing Web Services Logs and Traces
- Monitoring Sequences
- Configuring Web Services and Web Service Clients in the SAP NetWeaver Administrator , including required security settings
With Integration Engines you can go directly to the bgRFC Monitor (for Web service messages) and the

Transactional RFC and Queued RFC Monitor (for XI messages).
Once you have selected a component you can execute further activities. You can also do the following, irrespective of which component is selected:
- Testing the Runtime
- Testing Cache Connectivity
- Index Administration
- Selecting and Configuring Components
- Configuring Alerts
- Call an adapter log independent from communication channels.
  The log shows you the processing steps of the adapters that cannot be assigned to a specific communication channel.
  
  It consists of a table with a row for each adapter and columns for the adapter type, namespace, and frequency of processing errors. If you select an adapter, a second table is displayed, showing all entries for processing for this adapter.
- Performing Background Processing
- Security Archiving
- Registering Components in SLD
  
  Note
  
  Some of these tools are integrated directly into the SAP NetWeaver Administrator, whilst some of them are part of the Runtime Workbench.
  
  End of the note.
To start or stop PI-specific Java services (in Adapter Engines only), choose Java Services. The PI-specific services are preselected.
More information: Starting and Stopping AS Java Services.
You can find direct links to the Enterprise Services Builder and the
Working with the Integration Builder of the selected PI domains.