
To configure direct communication, you configure the relevant settings locally in the back-end systems of the Web service provider and Web service consumer that are involved.
For systems based on AS ABAP, you generally use the SOA Manager.
You can access the SOA Manager by using the transaction code SOAMANAGER in the back-end system.
More information: Working with the SOA Manager
For systems based on AS Java, you generally use the SAP NetWeaver Administrator.
SAP NetWeaver Administrator is the administration tool for Java-based back-ends involved in integration scenarios.
You can access the SAP NetWeaver Administrator by entering the following data in a Web browser:
http://<host><port>/nwa
Here the following represents:
<host> the host where the Application Server Java is installed.
<port> the HTTP port of the Internet Communication Manager. It consists of 5<Java instance_number>00. For example, if the instance number of the Java instance is 60, the HTTP port is 56000.
If the Web service provider and consumer are both based on AS ABAP 7.1 or a higher release, you can perform the configuration of the direct communication centrally in the Integration Directory, using a direct connection object (with an assigned sender channel of type WS).
You can use communication channels with adapter type WS only when you have chosen the SAP NetWeaver PI standard installation option. The reason is that this connectivity option is only supported by the Integration Engine.
More information: Connectivity
The configuration settings are propagated into the back-end systems by a caching mechanism, therefore making local configuration unnecessary.
More information: Configuring Direct Communication