Best Practices: Monitoring SAP PI Communication Channels
SAP PI adapters are used to exchange data with the SAP Process Integration. They transform messages so that they can be forwarded via communication channels.
The SAP Agent provides functions which can be used to handle adapters:
- Starting communication channels
- Stopping communication channels
- Querying information about communication channels
The functions XI_GET_CHANNEL and XI_SET_CHANNEL can be used in SAP jobs. Information about communication channels is stored as an XML document in the job report. For more information on formatting this data, see Script Functions for XML Elements.
Communication channels can also be monitored via Event objects of type Console (CONS Events). An event is triggered whenever the status changes.
Activate the XI interface with the SAP Executor's INI file parameters in the section [SAP_XI].
A Login object with valid login data is required for accessing the XI system. The XI user must be authorized to control the XI communication channels.
A user needs the following role to query the status of communication channels:
- xi_af_channel_admin_display
A user needs a role with the following action to start or stop communication channels:
- xi_af_channel_admin_modify
Since none of these actions are assigned to an ABAP role by default, you must explicitly assign them to a Java role which you then in turn assign to a java user or a user group. To do this use SAP NetWeaver Administrator with the quick link /nwa/identity.
We recommend using different Login objects for SAP and XI system if both are installed on the same host. Otherwise, the login entry is not unique.
AE JCL for XI
|
Script elements |
Description |
|---|---|
|
Lists communication channels |
|
|
Starts and stops communication channels |