Tue. Jun 2nd, 2020

Java-Based Messaging Components in SAP PI

2 min read

In a PI landscape, the Runtime Workbench (RWB) is used for monitoring messages within this landscape.
In addition, the Java-based messaging components (Advanced Adapter Engines, PCK) offer possibilities for generating trace files.

Monitoring with the Runtime Workbench or PCK

XI messages stored in the persistence layer of an Advanced Adapter Engine can be observed in the Advanced Adapter Engine’s monitoring tool, which can be accessed from the RWB. In an ordinary PI landscape, monitoring is performed by the message display tool of the RWB; in a PCK environment, it is performed by the local message display tool.

In both tools, you can restrict the monitoring permissions by three security actions called display, modify, and payload. Just like with the Integration Engine monitoring, the display action allows only message header monitoring, whereas the payload action also allows payload monitoring.

For the RWB, security actions must be assigned to the corresponding role for service com.sap.xi.rwb*rwb_mdt .

In all monitored Advanced Adapter Engines (and also in the PCK), security actions must be assigned to the role for service com.sap.xi.mdt*mdt .

If you want to specify the display permission for an RWB user, the easiest way is to either assign the corresponding ABAP role SAP_XI_MONITOR_USER_J2EE (for all monitoring permissions) or SAP_XI_DISPLAY_USER_J2EE (for header monitoring only) to this user in ABAP user management. As an alternative, you can define a new ABAP role that contains no Java monitoring role.

Tracing in the Advanced Adapter Engine

Besides being monitored, message payloads can also be traced in Advanced Adapter Engines or PCKs, depending on the trace configuration in the corresponding SAP NetWeaver Administrator. Since each message execution in the Advanced Adapter Engine or PCK includes a generic messaging service and an adapter-specific service, each message can be traced by both services.

In the Advanced Adapter Engine, message execution initiated by an integrated configuration for local processing can only be traced by the adapter-specific
message service. As a result it is not possible to trace message payloads.

You configure the tracing of the generic service by setting the trace location com.sap.aii.af.service.ms to severity debug with the Log Configuration function of the SAP NetWeaver Administrator (alias /nwa/log-config ). Correspondingly, you configure the tracing for the adapter-specific services under the node com.sap.aii.adapter .

To avoid unauthorized tracing here, make sure that only a restricted number of administrators have permission to use the SAP NetWeaver Administrator or to
access the AS Java file system where the trace files are stored.

Leave a Reply

Your email address will not be published. Required fields are marked *