Show TOC

Creating Contract ImplementationsLocate this document in the navigation structure

In each system, that is, separately for each actor, you have to implement one or more contract implementations based on the contract. The contract implementations reference the appropriate service providers and/or service consumers and define the message types.

Context

Table 1:
Communication Type Consumer Provider
Web Service

Consumer proxy

Service group

STCM

 Service definition
Web Service via Eventing Event provider (which is technically a consumer proxy for an event operation) Service definition
Note If your contract includes event operations, you can use separate service definitions for the Web service and the eventing operations, or you can use one service definition that covers both types of operations.
RFC Consumer proxy At the moment, only RFC consumers are supported.

Procedure

  1. Create a contract implementation using the Enterprise Services Wizard. In the wizard, specify for which contract and for which actor you want to create the contract implementation.

    You can also create a contract directly from a semantic contract by choosing Create Contract in the menu bar of the semantic contract editor.

    For more information, see Enterprise Services Wizard.

  2. On the Detail View tab in the proxy editor, specify an implementation for each message type.

    Specify the following information, depending on the type of actor:

    Table 2:
    Actor type Implementation type Required information
    Web service Consumer Consumer proxy Request message
    Service group Request message, which must be applicable for each service consumer contained within the specified service group.
    Single-target consumer mapping Target consumer
    Web service provider Service definition Request message
    RFC consumer Consumer proxy Request message

    In the field help, only appropriate consumer proxies, service groups, and service implementations are offered. When you enter them manually, the system checks your input.

    Note If the actor is the consumer, specify a consumer proxy with an appropriate request message or a single-target consumer mapping with an appropriate target consumer. If the actor is the provider, specify a service implementation with an appropriate request message. Note that you must remain within the same scope. More information on the scope is provided in the system documentation that you can find by choosing the Tips and Tricks icon in the proxy editor.
  3. Save the contract implementation and activate it.