Configuring the Communication Channel with Adapter Type WSLocate this document in the navigation structure

Use

You can configure the following types of communication with a communication channel with adapter type WS:

  • Direct communication between the Web service consumer and Web service provider.

  • Communication between the Integration Server and a connected Web service consumer or Web service provider.

More information:

Communication Channel (Adapter Type WS)

Take note that in order for scenarios in which Web service consumers and Web service providers communicate with each other to be configured completely that it will be necessary for further settings to be made in the relevant backend systems and that further configuration tools will have to be used. In addition to this, the specific procedure depends on the application case and the required security settings.

Procedure

You perform the following steps to specify the attributes of the communication channel.

1. Create a Communication Channel, Specify a Direction and Adapter Type

First create the communication channel, specify whether it is to be a sender or receiver channel and choose the adapter type WS(current version).

  1. In the Integration Directoty, select menu function Start of the navigation path Object Next navigation step New End of the navigation path.

  2. Call the Createdialog box for communication channels and specify the necessary key values (party and communication components).

  3. Choose the adapter type.

    For the current version of the adapter type WS, select the entry with the following values:

    • Name: WS

    • Namespace: http://sap.com/xi/XI/System

    • Software component version: SAP BASIS 7.30

      Caution

      Using the software component version you specify whether you want to use the current or an older version of the adapter type WS.

      You specify the older versions, which are still offered for compatibility reasons, by selecting the software component version SAP BASIS 7.10or SAP BASIS 7.11.

  4. Choose Copy.

    These are the default attributes:

    • Transport Protocol: HTTP 1.0

    • Message Protocol: WS 1.0

    • Adapter Engine: Integration Server

2. Define Type of Web Service Call

The type of Web service call specifies whether the call is made locally (same logical system), or remotely (different logical system). Depending on your choice, select or deselect the checkbox Local Call.

You can only configure this setting for a receiver channel.

The call type you select determines which other attributes you can define.

3. Specify Metadata Access (Receiver Channels Only)

With the following settings you specify how the Web service consumer accesses the metadata of the Web service provider that is configured by the receiver channel.

Note

The attributes for metadata access are only displayed for receiver channels and non-local calls.

More information: Configuring Metadata Access (Receiver Channels Only)

4. Specify Communication Security and Authentication Methods

With these settings you specify the fundamental communication security and with it a compatible authentication method. The authentication method determines how the Web service consumer authenticates themself with the Web service provider.

More information: Configuring Communication Security and Authentication Methods

Specifying SAML Assertions

When using the Single Sign-On with SAML (Authentication in Message)authentication method, you can specify SAML assertion.

More information: Specifying SAML Assertions

5. Specify the Source of the Response Encryption Certificate

When using asymmetrical message signature and encryption, you can define the source of the certificate further which is used to encrypt the response message.

This option only exists for cases where the receiver of the message (that sends the response message) is an SAP system .

More information: Determining the Source of the Response Encryption Certificate

6. Determine Technical Transport Settings

With these settings your determine the technical details for the connection.

More information: Configuring Technical Transport Settings

Using Previous Adapter Type Versions

For compatibility reasons, versions of the adapter type WS are offered which were available with previous releases of SAP NetWeaver Process Integration (SAP NetWeaver PI 7.1 or SAP enhancement package 1 for SAP NetWeaver PI 7.1). Use the older versions ( SAP BASIS 7.10or SAP BASIS 7.11) in cases where you have performed configuration work on the basis of such an earlier SAP NetWeaver PI release and you now want to proceed with this work on the basis of the current release.

For specific cases, SAP recommends using one of the previous versions.

Example

Using a previous adapter type version is offered, for example, when you have already executed configuration work on the basis of an installation of SAP NetWeaver PI 7.1 or SAP enhancement package 1 of SAP NetWeaver PI 7.1 and would like to continue with this work after upgrading to SAP NetWeaver PI 7.20.

It is generally recommended that you always select the adapter type version that corresponds to the oldest release of all the backend systems that are connected. When configuring direct communication between the Web service provider and Web service consumer you must determine the lowest backend release between the provider and consumer. When configuring Integratin Server communication you must determine the lowest backend release between the Integration Server, provider, and the consumer.

Example

Communication between an SAP system based on AS ABAP 7.11 and an Integration Server based on SAP Enhancement Package 1 of SAP NetWeaver PI 7.1: Use the current adapter type version ( SAP BASIS 7.11).

If addition you must use the older adapter type version if you want to configure direct communication between an ABAP-based and a Java-based backend system (irrespective of the release of the Java backend system).

By default you can only select the current adapter type version in the communication channel editor. To be able to select the older adapter type version, you must first import the relevant adapter metadata into the ES Repository.

More information: