Application Operations in SAP Solution Manager 7.2 provides System and Application Management capabilities for central monitoring, alerting, analytics, and administration of SAP centric cloud and on-premise solutions.
This wiki content has been moved to the SAP Solution Manager 7.2 expert portal. Any child pages of this wiki are deprecated and no longer maintained.
Documentation and Help Area of Central PI Monitoring
SAP NetWeaver Process Integration (PI) is SAP’s implementation of Service-oriented Architecture (SOA) middleware service bus; it facilitates the integration of business processes that span different software components, departments, organizations. Since 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 SAP Solution Manager 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.
The setup and the usage of central PI Monitoring differs significantly between SAP Solution Manager 7.1 and SAP Solution Manager 7.2. Please choose your release on the navigation panel to enter the corresponding wiki.
Monitor availability of PI component in entire PI domain (distributed across multiple multiple technical systems in your global landscape)
- Monitor PI communication channel availability for all central and de-central adapter engines in the entire PI domain from central SAP Solution Manager
- Monitor PI messages (errors, backlog and message flow) on all PI components in the PI domain
- Search for payload in PI messages across multiple PI components in the PI domain
- Alert erroneous PI messages based on PI alert rules (also single PI message
Continuous business availability – Centralized monitoring of PI domain helps to accelerate the problem resolution process. This leads to high availability of process Integration server and the data exchange between the systems are un-interrupted and hence the high availability of the application.
Central entry point – Growing PI landscape complexity and distribution leads to growing requirements towards a central monitoring approach
Reduced TCO – Simplification of operations processes by providing one single entry point for all component monitors for overall PI domain status. Additional drill down option provides detailed information up to host level. This reduces the overall problem resolution time and the number of resources involved in the investigation of issues.
Integration – Tightly integrated with other solution manager tools such as System Monitoring and Root Cause Analysis, Alerting Infrastructure, Notification and Incident Management
Production Resources freed – Central collection of monitored data relieves the production system from additional burden of monitoring.
Self check – Self check features provides availability of monitored components.
Message Monitoring – Operations support must be able to monitor and query all interfaces based on the date and time triggered, the sender and receiver systems, processing time, errors (if any), and other attributes. Messages will need to be uniquely identified so that they can be traced easily.
Payload Query – The system administrator (any other business / support personnel who need to) should be able to query messages based on the contents of the payload. For example, search for messages that have been sent to a procurement system by the Purchase Order Number or Vendor ID within a given date & time interval.