Originally published by Robert Laird.
Clarification on what’s happening with WSRR – IBM’s Service Registry & Repository product
There’s been uninformed speculation (hope?) by some of IBM’s competitors that WSRR is going away. End of life, no more support, and other nefarious statements intended to sow fear, uncertainty and doubt into current and potential future users of WSRR. Or, as Mark Twain said on being told that the NY Times had run his obituary, “reports of my death have been greatly exaggerated”!
As always in such situations, it’s best to look at the facts and get your information from those who know, which in this case is me, the Product Manager for WSRR. So, what is actually true is:
1. WSRR remains IBM’s offering for a SOA Registry & Repository product and is fully supported by a Level 1, 2, and 3 support structure which includes the WSRR development team.
2. WSRR delivered in March of 2015 its latest release, WSRR 8.5.5. This release is all about simplification of the product and user experience for service registry and repository including a single view of all service information, wizards to help and automate the service loading and consumption process, bulk loading of services via a spreadsheet, a simplified best practices design time governance process, and service consumption reports. Not bad for a product that the competition is trying to write the obituary on!
WSRR will continue to deliver on the simplification efforts from the 8.5.5 release, but that said, there is a relatively new product, called IBM API Management (APIM) that you should be considering if you are not already. The world has changed and using APIs is a really good idea! While WSRR is focused on System of Record (SoR) services, APIM supports both System of Engagement (SoE) and SoR. I’ll write another blog about SoE and SoR to go into those in more detail.
When you are ready to start experiencing the API Economy and SoE, use IBM APIM to manage and control your APIs. Your investment in services and services metadata in WSRR will allow you to proceed even faster with APIM, as service data can be imported into IBM APIM. As part of the IBM tooling to come, we will support coordination between WSRR and APIM of service and service metadata information including consumer-‐provider information for Impact Analysis.
IBM APIM is already a really excellent product for API runtime lifecycle including runtime processing of APIs and runtime policy enforcement on its DataPower gateway. IBM APIM already supports some level of design time service management which will be enhanced in 2015 to support design time lifecycle and
service Impact Analysis. This will position IBM APIM to be a single catalog for both API and service information.
So, users of WSRR will, metaphorically, be able to have their cake and eat it too. For those who want to use WSRR as is, the product will continue to be supported as IBM’S SOA Registry & Repository. For those who would like to use WSRR and IBM APIM together, their investment in WSRR services will be
leveragable with IBM APIM, and bi-‐directional coordination will be available to keep service information synchronized. For those who desire a single catalog to manage both APIs and services, IBM APIM will support that in 2015.
I am happy to answer questions and meet with any WSRR customers to answer your questions. Contact me at email@example.com or @Mountain_Bob