Creating Contract Implementations

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


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

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.

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:


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.

Save the contract implementation and activate it.