Jump to content

IBM WebSphere Service Registry and Repository

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Bkufluk2 (talk | contribs) at 16:50, 2 December 2010. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.


IBM WebSphere Service Registry and Repository
Developer(s)IBM
Initial release6.0 [1] 20 October 2006; 18 years ago (2006-10-20)
Stable release
7.0 [2] / 15 January 2010; 15 years ago (2010-01-15)
Written in Java
Operating systemAIX, Windows, Solaris, Linux, HP-UX, z/OS, IBM i, VMWare ESX / ESXi
Platformx86, x86-64, PowerPC, SPARC, IA-64, zSeries
Available inEnglish, French, German,Brazillian-Portuguese, Czech, Hungarian, Italian, Japanese, Korean, Polish, Russian, Spanish, Simplified Chinese, Traditional Chinese [3]
Type JEE Application
LicenseCommercial
Websitehttp://www-01.ibm.com/software/integration/wsrr/


IBM WebSphere Service Registry and Repository [4] (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 seperate entities. For example with a WSDL document, seperate 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 lifecycles 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 appropriate approvals at each 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 lifecycle 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. Supported ESB's include DataPower, WESB and WebSphere Message Broker.

Version history

Version 7.0

Business space ?

Version 6.3

Version 6.2

Version 6.1

Version 6.0.2

policy ?

Version 6.0

Inital release. Basic support for WSDL, XSD with a Web UI. Allows adding of properties, relationships and classifications.

References

Category:IBM WebSphere