IBM WebSphere Service Registry and Repository
Service registry / From Wikipedia, the free encyclopedia
Dear Wikiwand AI, let's keep it short by simply answering these key questions:
Can you list the top facts and stats about IBM WebSphere Service Registry and Repository?
Summarize this article for a 10 year old
IBM WebSphere Service Registry and Repository[4] (WSRR) is a service registry for use in a Service-oriented architecture.
Developer(s) | IBM |
---|---|
Initial release | 6.0 [1] 20 October 2006; 17 years ago (2006-10-20) |
Stable release | |
Written in | Java |
Operating system | AIX, Windows, Solaris, Linux, HP-UX, z/OS |
Platform | x86, x86-64, PowerPC, SPARC, IA-64, zSeries |
Available in | English, French, German,Brazilian-Portuguese, Czech, Hungarian, Italian, Japanese, Korean, Polish, Russian, Spanish, Simplified Chinese, Traditional Chinese [3] |
Type | JEE Application |
License | Commercial |
Website | http://www-01.ibm.com/software/integration/wsrr/ |
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.