sap pi 7 monitoring in single stack

5/22/2018 SAP PI 7 Monitoring in Single Stack

1/9

SAP PI 7.3 Monitoring Guide (Single Stack)This blog describes the technical monitoring transactions that must be carried out to support a PI system. The use of the transact

will enable the silent running of the PI system as they will highlight any current issues and detect any problems that may occur in

future. It is envisaged that these transactions will be run by second level support through out the working days on all systems in

production stack landscape unless otherwise specified. The document also captures the subsequent actions which should

undertaken should problems occur.

The central monitoring of SAP Exchange Infrastructure (PI) offers the option of executing various monitoring activities. Primarily, w

use the Runtime Workbench, the central tool for accessing PI monitoring.

Central PI monitoring offers the following options:

Message Monitor

Communication Channel Monitor

Performance Monitor

Java Proxy Runtime Monitor

Cache Monitor

Engine Status

IDOC Monitor

CPA Cache History

Channel-Independent LogsMessage Moni tor

Display message processing including aggregated and detailed information about status of messages, identify errors in message

processing and perform problem isolation. Manage individual messages by, for example, resending individual message versions.

Message Monitor could be accessed in one of the following ways:

Open a browser and go to http://:/pimonto access the Process Integration tools. Then choose Monitoring >> Adapter Engine >>

Message Monitor.

Click on the Message Monitor

In the message monitor, you can access the message overview or search for persisted or archived messages as described below.
http://scn.sap.com/servlet/JiveServlet/showImage/184079/file2.jpg


2/9

Message Status Overview :

Message Status Overview will allow you to get a quick overview of the entire message flows sorted by interfaces and status.

Overview of Messages and their Statuses shows:

1. Error

2. Scheduled

3. Success

4. Cancelled

Run the transaction for each component is the PI system every hour in the production system. The transaction should be run once a day in the

development and testing systems. (It vary depends upon the project requirements)

Database:

Set the time option to cover the last hour for the production system and last day for other systems and access the information by pressing displa

Analyze any errors or cancelled with errors and attempt to fix any problems.

Run the monitor regularly in the production system. The transaction should be run once a day in the development and testing systems (It vary

according to project requirements).

The Adapter Engines Messaging System (MS) receives the message, processes it and forwards it to the receiver. While the MS

processes the message, it passes several statuses:
http://scn.sap.com/servlet/JiveServlet/showImage/184025/File4.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/184213/File3.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/184025/File4.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/184213/File3.jpg


3/9

TO_BE_DELIVERED:

The state of message when it is initially handed over to the Messaging System.

DELIVERING:

The state of message when it has popped out of the MS queuing system and is in the process of being transmitted across the

or delivered to an application.

DELIVERED:

The state of message when it has successfully reached its intended recipient.

SYSTEM ERRORThe state of issues with the messages that are flowing through the PI side that can be stuck for several reasons.

HOLDING:

The state of an EOIO message that cannot be delivered until its predecessors have been delivered.

WAITING:

The state of a message that has been attempted to be sent at least once, failed, and is currently waiting for another attempt.

Statuses such as HOLDING or FAILED usually happen only for delivery semantics EOIO (exactly once in order) or BE (best effort)

System Overview:

Access Availability and Performance->System Overview->System Overview

This gives a broader status of all connected SAP applications(ECC, CRM, SRM) and services.

Status update on Java nodes, database connections, Memory Consumption monitored at one shot.
http://scn.sap.com/servlet/JiveServlet/showImage/183678/file1.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/183703/File5.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/183678/file1.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/183703/File5.jpg


4/9

Communication Channel Monitor:

Display the status of the communication channels and the corresponding adapters to get detailed and up-to-date runtime informatio

about individual communication channels.

Communication Channel Monitor could be accessed in one of the following ways:


Communication Channel Monitor.

Click on the Communication Channel Monitor.

The components of the PI system should be analyzed regular basis in the production system. The transaction should be run once a day in the

development and testing systems.

Analyze any errors and attempt to fix any problems.

Performance Monitor:

Monitor the performance of message processing on the Advanced Adapter Engine by inspecting the amount of processed data ove

various periods of time and the message processing time at individual adapter modules.

Performance Monitor could be accessed in one of the following ways:

Open a browser and go tohttp://:/pimonto access the Process Integration tools. Then choose Monitoring >> Adapter Engine >>

Performance Monitor.

Click on the Performance Monitor

Java Proxy Run Time Monitor:

Monitor the overall status of the Java Proxy Run time.

Java Proxy Run Time Monitor could be accessed in one of the following ways:

Open a browser and go tohttp://:/pimonto access the Process Integration tools. Then choose Monitoring >> Adapter Engine >> J

Proxy Run time Monitor.

Click on the Java Proxy Run time Monitor

You observe that the status of some of the components is not "green".
http://scn.sap.com/%3Chost%3E:%3Cport%3E/pimonhttp://scn.sap.com/%3Chost%3E:%3Cport%3E/pimonhttp://scn.sap.com/%3Chost%3E:%3Cport%3E/pimonhttp://scn.sap.com/%3Chost%3E:%3Cport%3E/pimonhttp://scn.sap.com/%3Chost%3E:%3Cport%3E/pimonhttp://scn.sap.com/%3Chost%3E:%3Cport%3E/pimonhttp://scn.sap.com/servlet/JiveServlet/showImage/183725/File6.jpghttp://scn.sap.com/%3Chost%3E:%3Cport%3E/pimonhttp://scn.sap.com/%3Chost%3E:%3Cport%3E/pimon


5/9

Cache Monitor:

Monitor cache objects in the SAP Net Weaver Process Integration run time caches of the Adapter Engine.

Cache Monitor could be accessed in one of the following ways:


Cache Monitor.

Click on the Cache Monitor

Engine Status:

Retrieve information about the messaging system of an Advanced Adapter Engine including data about message status, database

locks, queues, backlogs, event handlers

Engine Status could be accessed in one of the following ways:


Engine Status.

Click on the Engine Status

IDOC Monitor:

Monitor IDoc message traffic and meta data processed on the Advanced Adapter Engine.

IDOC Monitor could be accessed in one of the following ways:


IDOC Monitor
http://scn.sap.com/servlet/JiveServlet/showImage/185724/Adapter+Engine+Status.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/184188/Java+Proxy+Runtime+Monitor.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/185724/Adapter+Engine+Status.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/184188/Java+Proxy+Runtime+Monitor.jpg


6/9

Click on the IDOC Monitor

Procedure:

Choose the Message Monitor tab.

Choose one of the following search modes:

>> To perform a quick search, simply select one of the options in the Show drop-down menu.

>> In basic search mode, you can enter the number of the IDoc message in the Find field, and specify the message direction

and the time period.>> In advanced search mode, you can enter parameters of the IDoc or XI message as well as the start and end of the search

period.

Note:Using the message monitor you can search for IDoc messages processed with the IDoc adapter on the Advanced Adapter

Engine. You can add various IDoc parameters to the search criteria to find only those messages.

Channel Independent Log:

Display processing steps of adapters that cannot be assigned to a particular communication channel. Select an adapter to display

information about all entries for processing for this adapter.

Channel Independent Log could be accessed in one of the following ways:


Channel Independent Log

Click on the Channel Independent Log
http://scn.sap.com/servlet/JiveServlet/showImage/184113/File7.jpg


7/9

CPA Cache History:

CPA Cache History could be accessed in one of the following ways:


Channel Independent Log

Click on the CPA Cache History

Configuration:

PI 7.3Adapter User-Defined Message Search without TREX:

User Defined Message Search could be accessed in one of the following ways:

Open a browser and go to http://:/pimonto access the Process Integration tools

Then choose Configuration and Administration>> Click User Defined Message Search

Refer: SDN Web link
http://scn.sap.com/servlet/JiveServlet/showImage/185706/Cache+History.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/185725/Channel+Independent+Log.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/185706/Cache+History.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/185725/Channel+Independent+Log.jpg


8/9

Using SOA alternative way to access Monitoring :

Open a browser and go tohttp://[host]:[port]/nwato access SAP NetWeaver Administrator. Then choose SOA Monitoring PI IDoc Adapter

Monitoring.

Using Site Map :

Site map is a list of pages of a web site accessible to SAP users and it also lists down all the featuresin PI 7.3.
http://scn.sap.com/%5bhost%5d%5bport%5dhttp://scn.sap.com/%5bhost%5d%5bport%5dhttp://scn.sap.com/%5bhost%5d%5bport%5dhttp://scn.sap.com/servlet/JiveServlet/showImage/185731/Site+Map.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/185730/SOA.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/185731/Site+Map.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/185730/SOA.jpghttp://scn.sap.com/%5bhost%5d%5bport%5d


9/9

Troubleshooting Approach :

The troubleshooting approach explained in this document:

Define where the error is found or monitored

Define the failure points of the interface and the actual interface objects in ECC, Third Party System and PI

Testing and validating the communication object

Restarting messages (Getting the functional teams involved for data related issues and resending the messages if required

1.
http://scn.sap.com/servlet/JiveServlet/showImage/182795/File3.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/185732/Site+Map+Full.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/182795/File3.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/185732/Site+Map+Full.jpg

sap pi 7 monitoring in single stack

Documents