Identifying Sender and Receiver IBC Reference on Provider Side

Context

By default, the sender of a message passes the sender and receiver IBC reference in the SOAP header, unless it is suppressed by the corresponding setting in the domain system or logical port. Since it may not always be secure for the provider to rely on this sender and receiver information sent by the consumer, the receiver can define one of three methods to identify the sender IBC reference and the receiver IBC reference at runtime:

  • Identifying sender and receiver by authentication

    The communication framework determines the sender and receiver reliably on the basis of the authentication of the Web service user and the invoked Web service.

  • Identifying sender by authentication, receiver by SOAP header

    The communication framework determines the sender reliably on the basis of the authentication of the Web service user and the invoked Web service. The receiver IBC reference is taken from the SOAP header sent by the consumer.

  • Identifying sender and receiver by SOAP header

    In this case, both the sender IBC reference and the receiver IBC reference are identified by the SOAP header sent by the Web service consumer. This method is easiest as nothing has to be configured; but it is less secure than then the other two methods.

Procedure

  1. In SOA Manager (transaction code SOAMANAGER), choose Identification of Sender and Receiver on Provider Side on the Service Administration tab.
  2. Choose Create.
  3. In the dialog box, specify the following:

    • The method of identification:

      • Sender and receiver by authentication

      • Sender by authentication, receiver by SOAP header

    • The user with which the sender of the message logs on to the provider system.

    • The service definition.

    • Depending on the method, the sender IBC reference and receiver IBC reference or the sender IBC reference and the system.

      If only the sender is identified by authentication, specify the system to which this configuration needs to be passed. If the receiver is identified by authentication as well, you specify its IBC reference, which already contains this information.

  4. Choose Create.

Results

You have specified how the sender and receiver IBC references are identified for the specified combination of user and service definition.

Next Steps

Distributing Changes from the Central System to Domain Systems