Skip to Content

What would be the ESR strategy for customers who have both SAP NetWeaver Composition Environment 7.1 (CE 7.1) and Process Integration 7.1 (PI 7.1)?

 

 

 

By Elena Doll, SAP NetWeaver Product Management, SOA Middleware

 

 

 

Organizations consist of different business domains like Marketing, Finance, HR and Research & Development. They focus on diverse tasks while working on the same goals for the company. Therefore, business software can be provided specially adapted to the needs of different business areas.

 

 

When businesses move to a Service Oriented Architecture (SOA), they usually move all their business domains to SOA domains. It frequently makes no sense moving just some business domains like Finance or HR to SOA. For a smooth communication between business domains it is always better to have a homogeneous landscape based on SOA.

 

 

Business domains moving to SOA use the Enterprise Service Repository (ESR) in a decentralized way. This means they run ESR and sometimes even PI separately for every business domain. With this approach, the domains try to keep the independency and decisive power of the domains. Sometimes a real motivation to work constructively together is missing. In most of the realized SOA scenarios, every business domain has its own local ESR and usually one global PI as shown in the diagram below.

 

 

image

 

 

 

 

 

Moving to SOA includes the integration of all systems through PI 7.1 and the service enablement of the IT systems by exposing all applications as services and storing them in the ESR. The services become the core assets and form the basis of the IT and the entire business. To access and use the services, customers need tools like the SAP NetWeaver Composition Environment or any comparable tool.

 

But let’s take a look at the most common scenario when customer run SAP NetWeaver CE 7.1 and also PI 7.1. In this case the customer is in possession of at least two ESRs or “buckets” to store services since SAP delivers the ESR with both products CE 7.1 and PI 7.1. Since services are stored in the ESR they could be tied to CE 7.1 or the PI 7.1.

 

 

The question the customers face is which ESR they should use? PI 7.1 is the centre or the heart of the whole SOA landscape integrating all the systems and organizing the communication. The ESR where all the services are stored should be close to the heart that is close to the bus (PI 7.1). Every service call or communication goes through PI 7.1 anyway and never through CE 7.1. CE 7.1 is not integrated or specific to any business domain. CE 7.1 as a tool can be also installed locally on any computer and is used as a tool for developers to build applications out of services, should access the repository just like any other tool from outside. PI 7.1 on the contrary is centralized integrating the whole business, its ESR is the core and should be the chosen one.

 

 

 

 

 

 

image

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. Dipankar Saha
    Hi,
    Very relevant topic…Is there any option of integration between the different ESR from design-time perspective? What you mentioned in the blog is mostly runtime integration using the PI component. ESR typically refers to the design-time environment for modeling the services.
    Thanks,
    Dipankar
    (0) 
    1. Soum Chatterjee Post author
      Hi Dipankar,
      We allow interoperability of our service registry with other UDDI v3.0 registries at this point. We will most likely support federation of repositories and registries and ESB around 2010 or later. Integration will then be possible with other 3rd party repositories for change, create and updation of content.

      Hope this helps.

      Thanks
      Soum

      (0) 
  2. Prateek Raj Srivastava
    Thanks for sharing this Soumya.
    Suddenly being a PI consultant made me feel happy 🙂
    Is there a way in which PI ESR could communicate with other ESRs to either import or reference their objects?

    Thanks,
    Prateek

    (0) 
    1. Soum Chatterjee Post author
      Hi Prateek,
      We allow interoperability of our service registry with other UDDI v3.0 registries at this point. We will most likely support federation of repositories and registries and ESB around 2010 or later.

      Hope this helps.

      Thanks
      Soum

      (0) 
  3. Himadri Chakraborty
    Hello Soumya,

    Nice blog…

    In case we have PI7.11 and CE7.2 both, then should the strategy of choosing Central Service Registry be influenced by which one is of higher version?

    (0) 

Leave a Reply