Working with Service Definitions

Use

Once you have modeled the services of an application and how the they interact with each other, you can:

Create specified design objects in the ES Repository for the design objects you have modeled.
Specified here means that you define the structure of each modeled object in detail, for example, which operations a service interface comprises, and which data structure describes a particular message type.
Import the design objects if they are available in your landscape.

Note

You can also create the specified object types first. However, we recommend that you only start to do so once you have finished modeling the objects. It is then easier to derive the specifying objects.

See the prerequisites in the Enterprise Services Repository section.

Familiarize yourself with the Enterprise Services Builder .

Create the required interface objects such as service interfaces, data types, message types and so on, for your application.
More information: Developing Service Interfaces

Note

If a process component model or process component interaction model already exists, you can derive the names of the specified objects directly from the models.

More information: Modeling A2X Services , Modeling A2A Interactions .
If the design objects are already available in the WSDL, XSD, or DTD format, you can import them to the ES Repository and specify which parts of the schema to extract as the description for a message. This way, you can avoid recreating the design objects in the ES Repository.
More information: Working with External Definitions