Hi,
What is Service Registry?
Definition: Service Registry is a registry for Webservices that is located centrally within an SOA landscape. In simple words u201Cwhere are our services implemented?u201D can be identified by using Service Registry.
PI 7.1 contains a UDDI v.3 compliant Service Registry contains information about services provided in that landscape with references to the WSDL metadata relevant for those services and to the locations of the callable service endpoints.
How the Service Registry used in PI?
1. As a Webservice provider we can publish Webservice.
2. As a Webservice consumer we can search for and find Webservices for consumption.
3. We can test our Webservices.
4. Manage third party Webservices and classify them to provide them for consumption in our system landscape.
5. Providing Deployment information (i.e End point information).
Enterprise Services Repository (ESR):
To support strategic service oriented approach SAP provides a new Enterprise Service Repository. ESR is a central repository of information that contains all the services. ESR is a container, stores all the underlying Meta data of application objects like service interfaces and descriptions. The global data types, interfaces and business processes maintained in Enterprise service repository which can be reuse where needed. The first implementation of ESR and its associated editors come in SAP Netweaver04u2019s, which has been evolved from NetWeaver Exchange Infrastructure Integration Repository. Enterprise service repository is a design time repository of service objects for ESA. You can model all service design objects for a process and can reuse the data types and service objects which are already maintained. All enterprise services are published in a central Enterprise service repository so they can be used by anybody who really needs that service includes customers and partners.
The Enterprise Service Repository is the evolution of what it was known as the Integration Repository in XI. Now the Integration Repository is called the ESR and XI is called PI. Using the Integration Repository as foundation for the ESR made a lot of sense since many of the capabilities were already there: metadata storage, defining message types, data types, operations, etc.
ESR is just like Integration Repository for XI. Here you can design/define your Service Interfaces and Enterprise Services.
ESR is the central repository in which Service Interfaces and Enterprise Services are modeled centrally and their metadata is stored.
In simple words u201CWhat does the service do and what does it need?u201D can be answered from ESR.
ESR is used for: -
1. Definition of Processes and Services
2. Store Service Metadata
3. Central Modeling and Design Environment.
Global Data Types
Definition: Global Data Types are company-wide, defined data types based on international standards. They are based on the SAP methodology and are defined in a standards-based way in the ESR.
They are based on the ISO 15000-5 and UN/CEFACT CCTS standards and act as the semantic building blocks for service interfaces.
Global Data Types help you in standardizing service definitions across your organization and provide the key building blocks that can be reused across all your service definitions.
Global Data Types have been approved SAP-wide by the Governance Process for Business Content.
Global Data Types have been defined in the ESR and are described by XML schema.
Thanks,
Satya Kumar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.