WebSphere Service Registry and Repository
WebSphere Service Registry and Repository
(WSRR), part of the WebSphere Business Process Management suite, is a tool to catalog your services so that you can find them again. It doesn't host or run your services (you need WAS or WPS for that), but it tells you where they are. It can be used by people at development-time and programmatically at runtime.
WSRR is an IBM SOA product, specifically part of IBM SOA Governance. A service registry is very complimentary with an ESB for making services universally accessible and yet also controlling who can access what services.
Start with this intorduction to WSRR:
I use the term registry, not repository, yet WSRR uses both terms. Why? Besides being a registry of bindings for the addresses of services, WSRR also acts as a repository for storing and managing meta-info about services such as WSDL for the service interfaces. So WSRR is intended to (or at least can) act as your database of record for these service artifacts, a central place in your enterprise for storing and finding the latest, greatest set of stuff.
How to Use It
So how do you use WSRR? You can use it through the console GUI, both to register services and to browse at development time to find the services available. Some of this is shown in:
You can also customize the GUI:
You can also use it programatically at runtime. For an overview, see:
The programatic interface can be used in the following ways:
- Java client interface – EJBs to manage registered objects, govern their lifecycle, and browse their ontology
- Web services client interface – Most of the capabilities of the Java interface; based on SDO 2
- MBeans – Used to administer the repository
- Message Broker mediation – Enables a Message Broker message flow to query WSRR at runtime
- WESB mediation – Enables a WPS/WESB message flow to query WSRR at runtime
More Info
For more info:
