Service registry plays an important role in ‘e’SOA. For a successful SOA implementation, reusability of services needs to be ensured. In addition to defining the services based on non-proprietary data standards (CCTS based / GDTs in SAP), the required information intended to be reused should be published in an organized manner. A well defined and properly governed service registry should address security concerns and be open to the trusted service consumers for reuse. This provides a greater meaning and importance to a service registry than to be called it as the ‘yellow pages’ of enterprise services.
The most common advantage among the many is – Reduced development cost. The developers become aware of the new functionalities created by other development teams in parallel. Thus reduces redundant/ duplicate functionalities.
Service registry should be able to host services defined/ implemented in different systems in a heterogeneous landscape of the enterprise. An enterprise level service registry plays a core role in the SOA governance framework as it serves as a bulletin board for architects, BPXs and all who participates in the SOA ecosystem. Registry helps the providers and consumers to discover these services. Many vendors in the market provide service registry tools which is based on UDDIv3 – the ‘core’ standard for service registry. The various types of service registries in the market include – HP Systinet, webMethods Centrasite (Infravios xRegistry), – etc. SAP provides its registry and has been providing enhanced functionalities in each of its new versions. I would like to throw some light on the new features of CE Service registry in Ehp1 compared to the previous version. Service registry forms one of the areas (where BPX lives) that connects Business with IT.
The improvements in SAP CE7.1 Ehp1 service registry, which I am happy to find, are –
Guided step by step procedure of publishing services.
Now in Ehp1 CE 7.1
.Service groups. This is used in WDJ and integrated in other perspectives too for grouping the servics.
BeforeThis is a new option
- Provision of providing document URL as part of the service publishing process.
BeforeThis is a new option to provide the URL in an UI. A method for providing the documentation URL for a service has already been blogged in SCN.
- To create security permissions based on service classification and UME roles.
BeforeAgain a new option J.
- Provision to create permission templates as per the service classification and UME roles.
As Service registry is getting integrated with major perspectives in NWDS like Galaxy, VC etc.. I hope to find more enhancements in the coming versions.Here is my wish list for improvements in the order of priority –
- Provision of uploading WSDL files. Currently we have only the URL option.
- Subscription and notification API capabilities in the registry.
- More flashy UI’s with graphs to show the consumption, usage level e.t.c some thing similar to BO UI, RIA UIs etc. I am sure this can be easy with flash integration in WebDynpro ABAP.
- This could be a widget for experts to search for existing services in their ecosystem.
Looking forward to see more enhancements…
If you are new to service registry, you can find many blogs in SCN on publishing ABAP, JAVA and other services from R/3, NWDS and ESR into Service registry and also to consume the services in service registry through NWDS/ CE versions.