Select language:

Communication Channel Monitor


You use the communication channel monitor to call information about communication channels that are set up for the selected Adapter Engine, and to administrate these channels.

If you are running the Adapter Engine on a server cluster, the communication channels comprise multiple instances for the various cluster nodes.

  • The modify or payload actions for application*mdt are assigned to you.

  • You have started the Runtime Workbench, are in component monitoring, and have selected an Adapter Engine as the component.

  • On the Status tab page, you have chosen Communication Channel Monitoring to call the communication channel monitor.


The communication channel monitor displays the following information in a table. By using Configure Tables, you can show or hide individual table columns. To update the information displayed, choose Refresh . A selection box allows you to determine the number of visible table lines.



Communication Channel

Name of the communication channel


Status of the communication channel. The following statuses are possible:

  • Green ( ): Channel is started and functioning without errors.

  • Red ( ): Channel is started but errors have occurred.

  • Yellow ( ): Channel is started, but inactive.

  • Grey ( ): Channel is stopped.

  • Not available ( remove ): Adapter is not registered; no information about channel available.


Short Log

Explains the status of the communication channel and, in the event of an error, the type of error that has occurred.


Displays how the communication channel is controlled.

  • Manual

    You control the communication channel by choosing Start or Stop.

  • Automatic

    The communication channel is controlled by availability times [Page 74].

  • External

    The communication channel is controlled by an HTTP request.

Processing Errors

(not displayed as default)

Describes when the last processing errors occurred in the communication channel. If no errors occurred, the column remains empty.


Displays the communication party (if available) that is specified in the communication channel.


Displays the communication component that the communication channel is assigned to.

Adapter Type

Displays the type of adapter that has been selected and configured for the communication channel.


(not displayed as default)

Displays the namespace that contains the respective adapter type.


Specifies the direction of the communication channel: Sender or receiver channel.

Number of Nodes

(not displayed as default)

Displays the number of nodes if the communication channel consists of multiple instances on different nodes of a server cluster.


Channels with a yellow status ( ) are started, but are inactive on all cluster nodes of a server cluster. This means that a channel is not processing any messages, even though it has been started.

A channel has this status in the following cases:

  • The channel is configured as inactive in the Integration Directory (it can also only be reactivated in the Integration Directory).

  • The channel is set to inactive by the respective adapter (some adapters can do this and can also change this status if necessary).

  • You can define a filter to limit the communication channels that you want to monitor. To do this, enter the required selection criteria under Filter and choose Use Filter . If free entry is permitted, you can use an asterisk (*) as a placeholder.

    To reset the filter and, at the same time, refresh the list of selected communication channels, choose Initialize .

  • In the displayed table, you can sort the columns in ascending or descending order. To do this, choose the corresponding arrow symbols to the right of the column name.

    In the default setting, the table is sorted by the Status column, so that communication channels with errors are displayed at the top of the table.

  • By choosing Availability Time Planning , you can schedule the availability times for communication channels that you want to control automatically and not manually.

  • You can navigate to the Adapter Log , which is independent of the respective communication channel. This displays the processing steps of adapters that cannot be assigned to a particular communication channel.

    The log displays a table consisting of a line for each adapter, and columns for the adapter type, namespace, and occurrence of the processing errors. If you select an adapter, a second table is displayed, showing all entries for processing for this adapter.

  • You can select a communication channel from the displayed table and change how it is controlled. (If Multiple Selection is activated, you can select multiple or all communication channels).

    • You can activate or deactivate external control.

    • If external control is deactivated, you can control the communication channel as follows:

      • Manually, by choosing Start and Stop

      • Automatically, by scheduling availability times


      You cannot resend any messages that are sent to stopped channels. They are not rescheduled until the channel is started again.

      To control communication channels, you need the authorizations of user group SAP_XI_ADMINISTRATOR with the modify role. If you do not have this authorization, the relevant function pushbuttons are not displayed.

  • If multiple selection is deactivated (default), you can select a communication channel from the table to display detailed information about the status of the channel, as well as information about the channel administration. If the channel consists of multiple instances on different nodes of a server cluster, this information is provided for each cluster node.

    • The information that is displayed for the status of a channel on the individual cluster nodes is status information that is accumulated to give the overall status of the channel in the table of communication channels.

      If the cluster nodes have at least one status that is above all other statuses in the status hierarchy, the channel receives this status as the overall status. The possible statuses correspond to those in the table of communication channels and have the following hierarchy: (red), (yellow), (green), and (gray). A combination of green or yellow with gray is not possible.

    • The information displayed for the processing entries of the selected cluster node is current runtime information on message processing. You get to Message Monitoring by selecting the message ID displayed.

      Depending on the adapter used, the type and occurrence of the information can differ. The information forms the entry in the Processing Errors column in the table of communication channels. The newest result is taken from the table of the cluster nodes.

    • The information about channel administration displays when and by whom a channel was previously started or stopped. You can only start or stop a communication channel for an entire server cluster, not on individual cluster nodes. However, since errors can occur on individual cluster nodes during the execution of these actions, error information is also displayed for each cluster node.

    • If the channel is controlled by availability times, the Availability Times tab page is displayed. All other availability times that are relevant for this channel are also displayed. You can exclude specific availability times and, if necessary, reschedule them.


      Since only active availability times are displayed, it is possible that availability times do exist for the selected communication channel, even if none are displayed.

    • The information on the Settings tab page displays how often an attempt is made to send messages to this channel, and at what time intervals.

      The default settings are taken from the outbound properties for the Java Service XPI Adapter: XI.. You can overwrite and save these values. You can also restore overwritten values.

      Information about changes made to the settings is always displayed.


      The Settings tab page is only relevant for receiver channels and is therefore only displayed for channels of this type.