SAP Netweaver PI Monitoring using Solution Manager- Configuration Guide
What is PI Central Monitoring
Monitoring and controlling PI server/servers from a Centralised server.
Process Integration server is the heart of integration in an enterprise, it is very important to maintain high availability of the system for uninterrupted data exchange across the landscape. Central PI monitoring in Solution Manager 7.1 provides unified alert notifications, exceptions and status of PI components from a single entry point. It also provides options to navigate to details of such exceptions in the respective host system. It becomes easier for addressing the issues more quickly and efficiently.
Advantages of PI Central Monitoring
- Growing PI landscape complexity and distribution leads to growing requirements towards a central monitoring approach
- Reduce the TCO by simplification of the operations processes
- Enable tight integration with
- System Monitoring and Root Cause Analysis
- Alerting Infrastructure
- Notification – / Incident Management
- Relieve Productive Systems from individual Monitoring activities by a central collection of monitoring data
- Reduce the time
- For regular system health checks
- For hand-over procedures
- From incident detection to root cause
Central Monitoring Tools Integrated
The below are the various tools available on Solman and which support the entire Software Life Cycle Management.
The PI Monitoring Tools are available under Technical Operations.
Technical Operations – Tools include
- Monitoring and Notify tools like PI Monitor, BI Monitor, Solman Self Monitor, Alert Inbox Configuration etc
- Analyzing Tools includes End-to-End Analysis, Workload Analysis, Exception Analysis, Trace Analysis
- Administrate Tools supports Solman Administrative functions
- Reporting tools like EWA, Technical Reports, Business Reports
Overview of Setup Procedure for Central PI Monitoring
PI Monitoring works in context of PI Domain
SAP Solution Manager must know all the landscape information and establish connectivity to all involved systems and components.
1. Synchronizing the content of PI SLD into Central SLD of Solman (LMDB)
First of all a sync between PI SLD and central SLD of Solman is required, for this purpose add PI SLD in central SLD and do a content synch (full synch). As this will serve the purpose of sending SLD information, hence no SLD Bridging is required. The SLD Bridge information in PI SLD to Central SLD should be removed from Data Supplier.
2. Synchronize the content PI SLD into LMDB
The Landscape Management Database (LMDB) is a directory of elements of a system landscape. Using SOLMAN_SETUP Tcode, LMDB and Central SLD should be synchronized. LMDB provides information about the entire system landscape at a central location. There are different patterns for configuring it and depends on system performance and requirements to decide which pattern would be suitable.
We could have a central SLD and copy the SLD contents of System 1, System 2 and System 3 and synchronise the contents of Central SLD directly to LMDB of SAP Solman.
Having Central SLD and synchronising the contents of Central SLD to SLD of Solman and then synchronise it to LMDB .
Here the Performance is high but the there is a synch gap of SLD Solman updates to Solman LMDB.
Directly synchronising the contents of each system SLD to local SLD of Solman.
3. Managed System Configuration
SAP Solution Manager should be connected to all systems in the system landscape. All the systems which are connected to the SAP Solution Manager are called managed systems. The SAP Solution Manager is the central location for the management and setup of the connected managed systems, so connection to those systems is required. In SAP Solution Manager this is usually ensured by using a trusted RFC with the user.
The following Setup and configuration steps are necessary
a) Product Selection – Here define the PI instance
b) Define Trusted RFC connection – for ABAP systems RFC destinations are created.
c) Diagnostic Agent Creation- For each PI instance Diagnostic Agent is required.
d) Define PI scope for monitoring- Here for each PI instance the different part of the monitoring component is mentioned. e.g- IE, AE, Proxy Runtime etc.
Technical Monitoring and Alerting tool on Solman
The following are the applications supported on Monitor & Alerting tool
Central PI Monitoring -Dual Monitoring
Central PI Monitor through Solman gives us the flexibility of Dual Monitoring i.e. the systems could be either monitored using Central Monitoring and also Local (Traditional) Monitoring of the systems are still available.
Note:- The Central PI Monitor is not real time. Also we could not take actions on Central Monitor Directly.
Alternatively it has an option to access the local PI server and actions could be performed from there.
For PI Monitoring Usage and Guidelines refer document below:-