Creating Contract Implementations
This option allows you to provide contract implementation details such as project, package, name, Enterprise Services name, Enterprise Services Namespace, prefix, contract, and actor details.
Context
You create a contract implementation to reference each actor involved in a contract. Based on the contract definition, an actor can be a provider of service or a consumer of service. A contract implementation references each actor, either as a service provider or as a service consumer.
If the actor is a service provider then contract implementation defines a service definition. If the actor is a service consumer then contract implementation defines consumer proxy, single target consumer mappings or Service Group.
Prerequisites- A contract is available. For information on creating a contract, see Creating Contracts.
- A service consumer proxy is available. For information on creating a service consumer proxy, see Consuming a Web Service Using the Enterprise Services Repository.
- Access the Enterprise Services wizard. For information on using the wizard, see Accessing the Enterprise Services Wizard.
- Select Contract Implementation.
- Click Next.
The New Contract Implementation wizard appears.
- Enter the following details:
- Package name
- Name
- Prefix, if required
- Contract and Actor details.
- Proceed with the wizard and complete the task.
Contract Implementation and its operations appear in the editor.
- Select an operation.
Communication Type Description RFC The Details section displays Consumer Mapping (Single Target) as the only supported implementation type. Web Service The Details section displays the related message type details. - Continue with either of the options based on the operation that you selected:
- To set up an RFC-based operation:
- Select a single target consumer mapping with an RFC consumer as a target proxy.
- To set up a Web services based operation:
- Expand the selected operation.
- Select a message type.
- In the Details section, based on the message type selected, appropriate options appear. The table below lists the message type and their respective options:
Selected Message Type Action Required Provider message type Click the Browse button to select a service provider. Consumer message type Select any one of the following implementation types: - consumer proxy with an appropriate request message
- single-target consumer mapping with an appropriate target consumer
- service group containing the target consumer
- To set up an RFC-based operation:
- Save the contract implementation.
- On the top right corner of the proxy editor window, click
( Activate ABAP Object) to activate the contract implementation.