Controlling a Communication Channel Externally 

Use

You can also control communication channels externally, by connecting to an external scheduler for example. You switch to external control in the Communication Channel Monitor.

Prerequisites

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.

Procedure

To control communication channels externally, you use an HTTP GET or POST request to the following URL:

http(s)://host:port/AdapterFramework/ChannelAdminServlet?party=party&service=service&channel=channel&action=action

The parameters in italics are described in the following table:

Parameter	Description
party	Identifies the party of the channel to be administered. You can use an asterisk (*) as a placeholder to administer several channels simultaneously.
service	Identifies the communication component of the channel to be administered. You can use an asterisk (*) as a placeholder to administer several channels simultaneously.
channel	Identifies the name of the channel to be administered. You can use an asterisk (*) as a placeholder to administer several channels simultaneously.
action	Identifies the action to be executed (start, stop, or status). You use the start and stop actions to start and stop the channels. You can use the status action to query the status of one or more channels.

The XML structure of the HTTP response is documented in a document type definition (DTD) and an XML schema definition (XSD). You can call this information using HTTP at the following addresses:

●      http(s)://host:port/AdapterFramework/channelAdmin/ChannelAdmin.dtd

●      http(s)://host:port/AdapterFramework/channelAdmin/ChannelAdmin.xsd

In the event of internal runtime errors, the HTTP response code is set to 503.