June 01, 2010, 1:18 PM — SAP ESR and SAP SR are the core tools for the SAP SOA modeling and implementation. In this blog, we provide the evolution and role of the SAP ESR for SAP SOA implementation.
What is SAP ESR
•SAP ESR is the evolution of Integration Repository (IR) in SAP XI. IR was already representing the end points as message interfaces. Message Interfaces were already exposed as WSDL. SAP has added the Modelling capability for Process Component Models (which is an extension on top of the earlier Integration Scenarios), and streamlined the usage of end points (now called Service Interfaces). It has also streamlined the usage of data types which are now called global data types.
•The service organization concept is similar to that of IR. All Service Interfaces are within a SCV and a namespace.
•SAP ESR provides the advantage of providing a consistent naming convention of Service Interface.
•Enterprise Service Builder (ES Builder) offers a modeling environment to create various models in the Enterprise. It was earlier called the Integration Builder in the SAP XI environment.
Salient features of SAP ESR:
•ES Builder allows to create Process Component Model (ProComp Model)
•In SAP NW 7.0 (2004s) and SAP NW ‘04, service interfaces have one operation per service. In SAP NW PI 7.1 the Enterprise Services Repository offers multiple operations per service.
•Global Data Types: Approved SAP-wide using the Governance process. Reusable semantic building blocks for service interfaces and message types.
Why to use SAP ESR:
•SAP ESR is the central repository for modeling the service interface. We model the service operations, and their request/response structures. This allows us to have a CENTRAL enterprise wide repository for managing these definitions.
•SAP ESR provides the capability for organizing the service definitions based on software components, their versions and namespaces. It also allows us to maintain service versions (since services invariably would get revised over time).
•Enable SOA design governance across the organization. We can model the Process Component architecture models in ES Repository. From the ProComp models, we can drill down to standards based service interface design (Service Metadata). The service interfaces are based on GDTs that provide resusable uniform representation of business structures.
SAP ESR is positioned to be the central enterprise wide repository for managing all service definitions for SAP and nonSAP services.
Our recommendation for SAP customers is to use SAP ESR for modeling and managing all SOA service definitions for SAP and non-SAP services across the enterprise.
Manish Agarwal is SAP Program Manager, Nagarro, Inc.