This blog describes the technical monitoring transactions that must be carried out to support a PI system. The use of the transactions will enable the “silent running” of the PI system as they will highlight any current issues and detect any problems that may occur in the future. It is envisaged that these transactions will be run by second level support through out the working days on all systems in the production stack landscape unless otherwise specified. The document also captures the subsequent actions which should be undertaken should problems occur.
The central monitoring of SAP Exchange Infrastructure (PI) offers the option of executing various monitoring activities. Primarily, we use the Runtime Workbench, the central tool for accessing PI monitoring.
Central PI monitoring offers the following options:
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:
Message Status Overview :
1. Error
2. Scheduled
3. Success
4. Cancelled
Database:
The Adapter Engine’s Messaging System (MS) receives the message, processes it and forwards it to the receiver. While the MS processes the message, it passes several statuses:
● 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 wire or delivered to an application.
● DELIVERED:
The state of message when it has successfully reached its intended recipient.
● SYSTEM ERROR
The 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:
Communication Channel Monitor:
Display the status of the communication channels and the corresponding adapters to get detailed and up-to-date runtime information about individual communication channels.
Communication Channel Monitor could be accessed in one of the following ways:
Performance Monitor:
Monitor the performance of message processing on the Advanced Adapter Engine by inspecting the amount of processed data over various periods of time and the message processing time at individual adapter modules.
Performance Monitor could be accessed in one of the following ways:
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:
You observe that the status of some of the components is not "green".
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:
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:
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:
Procedure:
>> 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:
CPA Cache History:
CPA Cache History could be accessed in one of the following ways:
Configuration:
PI 7.3 – Adapter User-Defined Message Search without TREX:
User Defined Message Search could be accessed in one of the following ways:
Refer: SDN Web link
Using SOA alternative way to access 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.
Troubleshooting Approach :
The troubleshooting approach explained in this document:
1.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
37 | |
10 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
2 | |
2 |