The WSO2 Governance Registry is a fully open source, SOA-integrated registry-repository for storing and managing metadata related to service artifacts and other artifacts. There are two broad categories of artifacts found in the WSO2 Governance Registry.
- Resources
- Collections
A resource is any artifact from WSDL files to XML, Word/Excel documents, JPEG Images, etc. Within the WSO2 Governance Registry, resources under a logical entity can be grouped into a "collection" and stored. Every resource in the WSO2 Governance Registry becomes a center for social activity.
Eschewing the complexity (and WS-* focus) of specs like UDDI, the Governance Registry uses Atom Publishing Protocol (via Apache Abdera) to offer a standard and simple RESTful remote interface, which can be accessed easily by custom code, feed readers, and browsers. It has been designed to both encourage "grass-roots" community around your data and also to allow for IT-friendly governance.
The WSO2 Governance Registry is available under the Apache Software License version 2.0, and can be either used as a complete product or in combination with components of other WSO2 products. User-specific components, extensions or UIs to the Registry can be easily added as Carbon components.
WSO2 Governance Registry main functionality falls under two categories:
- Content repository
- Governance Framework
...
The content repository virtually can hold any type of content. But in order to give prominent support for SOA-type services, it is cased as follows:
- Special UI to capture both technical and non-technical details related to the services
- Separate upload UI's for Policy, WSDL and Schema, which are tightly related to SOA type services
- Built-in validation for Policy, WSDL and Schema
...
There are two ways to update Governance Registry with service details:
- Using Governance Registry's UI
- Uploading WSDL
...
If you choose the first way and add a service bearing the name "OrderRegistration" with the namespace as org.acme.services, a resource will be created inside /governance/services/org/acme/services/OrderRegistration with application/vnd.wso2-service+xml as the media type. Similarly, you can upload a WSDL to the system and Governance Registry will automatically create a service resource under /governance/services collection. Additionally, if a given service has WSDLs/Schema/policies, Governance Registry will automatically upload them and create associations between related artifacts(resources).
So monitoring/querying of the location /governance/services gives vision of the services registered within Governance Registry. Another option is to enable notifications (e-mail, SOAP, HTTP POST) for this repository location. For advanced users, Governance Registry supports writing custom handlers for given media types.
...
The WSO2 Governance Registry version 4.5.1 is the successor of version 4.5.0 and built on Carbon 4.0.2 base platform. It has several defect fixes included in it. For a list of fixed defects in this release, refer to: WSO2 Governance Registry 4.5.1 - Fixed Issues.
Enhancements:
- Performance enhancements due to refactoring the Carbon context. (Inherited from new and enhanced Carbon 4.0.2)
...