Managing Services in the Enterprise Services Repository 

Use

The Enterprise Services Repository (ES Repository) is a central repository where you define, access, and manage SOA assets such as services, data types, and so on. The repository stores the definitions and metadata of enterprise services and business processes. It also provides a central modeling and design environment for creating, aggregating, and using enterprise services. You use the Enterprise Services Builder (ES Builder) to access the objects in the ES Repository.

For more details on the ES Repository, refer to the SAP Developer Network (SDN) at https://www.sdn.sap.com → SOA Middleware →Modeling and Design.

The Enterprise Services Repository contains object types that are relevant for both SAP NetWeaver Process Integration and SAP NetWeaver Composition Environment. Only a subset of the object types in the ES Repository is relevant for SAP NetWeaver Composition Environment. The object types displayed in the ES Builder are restricted by means of the usage profile. For more information, see Usage Profile.

Prerequisites

·        Familiarize yourself with the basics of the ES Repository.

More information: Understanding the Concepts

●      Understand how to organize and manage content in the ES Repository.

More information: Organizing and Managing Content in ES Repository

●      Software component versions are the smallest shipment units that can be delivered using the objects of the ES Repository. To be able to develop within a software component version that is relevant for shipment, it must be maintained in the software catalog of the System Landscape Directory (SLD). SAP products and the corresponding software component versions are already maintained in the SLD. You can also enter external products, software components, and software component versions in the SLD.

More information: Software Catalog

In addition to the shipment-relevant software component versions, you can also work with a local software component version in the ES Repository initially; this does not have to be maintained in the SLD.

Procedure

...

       1.      Begin by browsing through the ES Workplace, on SDN, to discover the services delivered by SAP. You can download and import the required content to work with them.

More information: Managing Enterprise Services Delivered by SAP

       2.      If you do not find the required services in the ES Workplace, you can develop your own enterprise services or reuse your existing services, if available. You begin by modeling your application in the ES Repository. In the subsequent step, specify in detail the design objects your application requires and continue with the implementation.

More information: Defining Custom Services

       3.      The Integration Server provides application integration services (such as mappings and integration processes, for example) that you can define by means of additional object types in the ES Repository.

More information: Defining Design Objects for Mediated Communication

You can develop applications integration services only if you have SAP Netweaver Process Integration installed in your landscape.

       4.      The services published from the ES Repository are available in the Services Registry.

More information: Discovering services in the Services Registry