Creating Contracts from Schemas

You can export an XML description of a contract and use this as the basis for creating a contract in another system. Contract must be available in both systems involved in establishing a contract or in client systems that need to communicate with each other. If you have modeled a contract in one system, you can copy it to another system using an XML file. You can also transport contracts across your system landscape.

Prerequisites

• A semantic contract is available on the same system. You can create the semantic contract from a schema as well. For information on creating a semantic contract from a schema, see Creating Semantic Contracts from Schemas.
• A service consumer proxy is available. For information on creating a service consumer proxy, see Consuming a Web Service Using the Enterprise Services Repository.

Exporting a Contract Schema Procedure

1. Access an ABAP package. For information on accessing an ABAP package, see Accessing an ABAP Package.
2. Navigate to the identified contract.
3. Open the contract.

   The contract editor window appears.

4. Click the Source [Read-Only] page.

   The schema or the XML definition of the contract is displayed.

5. On the top right corner of the editor, click (Export as WSDL).

   The Save As window appears.

6. Save the file and send it to an ABAP system.

Creating Contracts from XML Files

The key steps for creating a contract from XML files are:

1. Creating a proxy using schema
2. Selecting a communication type

Procedure

1. Creating a proxy using schema.
   1. Access the Enterprise Services wizard. For information on using the wizard, see Accessing the Enterprise Services Wizard.
   2. Select Contract.
   3. Click Next.

      The New Contract wizard appears.

   4. Enter the following details:
      • Package name
      • Name
      • Prefix, if required
   5. Select Local WSDL File as the source.
   6. Click Next.
   7. In the Local WSDL wizard, click Browse...

      The Open window appears.

   8. Browse to the WSDL file location.
   9. Proceed with the wizard and complete the task.

      The contract and its respective operations appear in the editor window.

2. Selecting a communication type.
   1. In the Details section of the contract editor, you can:
      • view information about participating actors
      • select a communication type for the contract
   2. To provide operation details, select an operation.

      Selected Communication Type	Action Required
      RFC	Only the Select button for the RFC Consumer field appears enabled. Use the Select button to provide RFC Consumer and RFC Operation details.
      Web Service	The Browse buttons of the Request and Response Message Type fields and the Add button of the Fault Message Type field appear enabled.

   3. Save the contract.
   4. On the top right corner of the proxy editor window, click ( Activate ABAP Object) to activate the contract.