Configuring the Web Service Runtime 

Use

You can configure scenarios in which Web service consumers or Web service providers appear as communication partners.

Both of the following two communication types are supported for Web service scenarios such as these:

●      Direct Communication

In this case the Web service consumer calls a Web service provider directly.

More information: Configuring Direct Communication

●      Integration Server Communication or Enhanced Communication

In this case the Web service consumer calls the Web service provider using an Integration Server.

This is a special case of the communication scenario described under Configuring Communication Using the Integration Server.

You can also realize scenarios in which a Web service consumer uses the Integration Server to connect with a communication partner who expects a protocol or format that is supported by Process Integration Connectivity (for example, an RFC call). The same is true in the opposite direction.

Procedure

You can use the following tools to configure the basic communication settings.

●      Integration Directory

Required for configuring Integration Server communication.

In this way you use the sender agreement to specify the inbound processing of the Web service call at the Integration Server. You assign a sender communication channel (adapter type WS) to the sender agreement, which, at runtime, converts the Web service call to a message format that the Integration Server 'understands'

Using a receiver agreement you can specify the outbound processing of the message that is to be sent from the Integration Server to the Web service provider. Accordingly, a receiver communication channel (adapter type WS) 'translates' the message format of the Integration Server into a Web service call at the receiver side.

More information: Configuring the Communication Channel with Adapter Type WS.

If systems that communicate with each other are based on AS ABAP (from AS 7.10 upwards), you can create the complete configuration settings for the Integration Server and the back-end systems involved in the Integration Directory. In this case the configuration settings are distributed to the back-end systems involved using cache notifications so that local configurations settings are no longer required there.

If the above named condition has been fulfilled for systems that communicate with each other, you can also execute the complete configuration for direct communication in the Integration Directory.

If the back-end systems involved do not fulfill the condition stated above and additional security settings are to be configured for communication, you will need to use other tools and procedures to complete the security. Note the reference below to additional information in the SAP Developer Network (SDN).

More information: Integration Directory

●      SOA Manager and SAP NetWeaver Administrator

You can configure the direct communication of two backend system locally in the SOAMANAGER transaction.

For more information, see SOA Manager.

Service providers and service consumers can be configured in the SAP NetWeaver Administrator.

More information: Configuring Web Services and Web Service Clients in the SAP NetWeaver Administrator

●      Transactions in Back-End Systems (ABAP)

If you want to configure communication between two ABAP-based back-end systems, further transactions are required in the back-end systems involved to complete the configuration. Note the reference below to the additional SAP Developer Network (SDN) document.

Note that this procedure depends in detail on the specific usage case. Also, the configuration of special security settings can require additional tools.

You can find a detailed description of the procedure and the tools to be used in a separate guide. For more information, refer to the SAP Developer Network (SDN) under https://www.sdn.sap.com/irj/sdn/soa-management.  In the Knowledge Center on the SOA Management page, choose the Configuration and Monitoring service and on the following pages of the document, SAP NetWeaver Process Integration 7.1 - Configuring Web Service Scenarios (Guide).