Configuration Objects (Direct Communication)

Use

in this section you find a summary of the configuration objects that are required when you want to configure direct communication between a Web service consumer and a web service provider without any runtime engine interconnected. The relevant configuration objects are highlighted in blue in the graphic.

Figure 1: Configuration Objects Relevant for Direct Communication

The objects required to execute the current configuration tasks are listed in the following table.

Tasks	Relevant Objects
Defining a collaboration profile In the collaboration profile you specify which components communicate with each other and what their technical communication capabilities are.	Communication party (party for short) Communication component Communication channel
Defining a direct connection With a direct connection you configure the direct communication between the sender (Web service consumer) and the receiver (Web service provider). You assign the receiver channel of the receiver system to the direct connection. Caution This option is only provided for channels with adapter type WS .	Direct connection

Tasks

Relevant Objects

Defining a collaboration profile

In the collaboration profile you specify which components communicate with each other and what their technical communication capabilities are.

Communication party (party for short)

Communication component

Communication channel

Defining a direct connection

With a direct connection you configure the direct communication between the sender (Web service consumer) and the receiver (Web service provider).

You assign the receiver channel of the receiver system to the direct connection.

Caution

This option is only provided for channels with adapter type WS .

Direct connection

When you activate the configuration objects, the configuration settings made in the Integration Directory are transported to the back-end system on which the Web service consumer or Web service provider are installed.

Caution

Note that complete configuration of scenarios of this type is only supported at this time in the Integration Directory for back-end systems that are based on AS ABAP 7.10.