IBM WebSphere Service Registry and Repository (WSRR) is a service registry for use in a Service-oriented architecture.
It runs as a Java Enterprise Application on IBM WebSphere Application Server.
It provides functionality to store and retrieve service-metadata. WSDL, XSD, SCA Modules and Policy documents can be loaded and parsed into separate entities. For example, with a WSDL document, separate entities are created for service, binding, portType etc. XML and binary documents can be loaded as single entities. These entities can then be decorated with additional data in the form of properties, classifications and relationships. Classification systems defined in OWL are supported. Custom object types can be modelled in OWL such as service contracts, SLAs and SLDs.
Entities with the registry can be managed using life cycles defined in SACL in order to provide service governance. The life cycle can track the state of a service, for example through Development, Test, QA and Production, allowing for approval and checks before moving to the next stage.
APIs
The product has Web service, JEE EJB and ATOM/REST based APIs for accessing and manipulating data within the registry.
UDDI synchronisation can be enabled to provide integration with products supporting the UDDI v3 API.
Extension points
Validators, Modifiers and Notifiers. There are defined extension points (similar to a User exit) which allow a custom piece of code to be run within the product when an event occurs. This could be when an object is created, updated or deleted, or when a transition occurs from one life cycle state to another.
Integration
When combined with an ESB, can provide dynamic endpoint lookup. This allows services to be redirected based upon information retrieved from the registry. ESB's which include primitives to support this out of the box include DataPower, WESB and WebSphere Message Broker. Other ESB's can use one of the WSRR APIs to look up the endpoint information.
Version history
Version 8.5.6 (October 2015) This release added a user interface enhancement that enables users to display their REST services in a Swagger viewer, when they describe their REST services using Swagger 2.0.
Mediation runtime policy ordering allows WSRR, as the policy administration point, to now specify the order in which Service Level Definition (SLD) policies are enforced in DataPower.
Custom, runtime policy filters provide WSRR, as the policy administration point, the ability to insert custom Message Content Filters (MCF) into the response to allow the DataPower Multi-Protocol Gateway (MPGW) to perform advanced functions.
Added support for POWER8 Little-Endian on SUSE Linux™, Red Hat Linux (RHEL), and Ubuntu operating systems.
Users can test their promotion configuration from the governance master to runtime before actually performing a promotion.
Users can download all relevant documents, including SOAP (WSDL) and REST (Swagger 2.0) service interfaces, as a single zip file.
The ability to insert a random UUID into any property by using the configurable modifier. Documentation is created regarding how to use the UUID to create context and consumer IDs when an SLA and version are created for a service.
The 8.5.6 release was a "mod pack" which means it can be applied as a fix pack to an existing 8.5 installation.
Version 8.5.5 (March 2015) This release added user interface enhancements that enable: Simplified SOAP service registration by new wizards and a new editing User Interface. Simplified view of a service on one page, using tabs to show endpoints, interfaces, and details. Simplified registration of a consuming service or application, by a new wizard.
A bulk load tool which loads a spreadsheet containing service definitions into WSRR and creates the service definition objects in WSRR.
A simplified service management profile which reduces the steps in the life cycle for services, service level definitions and applications. The profile also has simplified labels for states of objects and transitions to move between states.
Simplified promotion process where all objects on the target system are updated when a promotion happens to that system, rather than the previous behavior.
Performance improvements when loading large (around 1 MB or larger) WSDL and XSD documents.
The 8.5.5 release was a "mod pack" which means it can be applied as a fix pack to an existing 8.5 installation.