This documentation is for WSO2 Governance Registry 5.1.0. View documentation for the latest release.
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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. WSO2 Governance Registry is fully open source and is released under Apache Software License Version 2.0, one of the most business-friendly licenses available today. 

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 an on-going project. It undergoes continuous improvements and enhancements with each new release, to address new business challenges and customer expectations. WSO2 invites users, developers and enthusiasts to get involved or get the assistance from our development teams at many different levels through online forums, mailing lists and support options. We are committed to ensure you a fulfilling user experience at any level of involvement with the WSO2 Governance Registry. 

You can use WSO2 Governance Registry either 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.


There are two broad categories of artifacts found in the WSO2 Governance Registry as follows.


 A resource is any artifact from WSDL files to XML, Word/Excel documents, JPEG Images, etc. Every resource in the WSO2 Governance Registry becomes a center for social activity.


 A collection is a group of resources that falls under a logical entity, and are stored within WSO2 Governance Registry. 

Main functionality

WSO2 Governance Registry main functionality falls under the following two categories.

Content repository

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

Governance framework

The governance framework embodies the following set of governance features which allows you to govern the artifacts stored in the content repository.

  • Define any type of governance asset
  • Customizable repository extension points, executable via manual intervention (aspects) and by the framework (handlers) along with relevant evaluation criteria (filters)
  • Integrated with 3rd party products and external systems
  • Repository APIs: JCR
  • Registry APIs: REST, UDDIv3, JAXR
  • Governance APIs: REST, Atom/AtomPP, SOAP
  • Centrally integrated with the latest version of WSO2 Enterprise Store 2.0 and WSO2 API Manager
  • Create and manage registry resources, APIs and Swagger instances with the newly introduced Governance Centre UI
  • Installation provision for API-M, enabling API publisher and store functionalities, including API creation, publishing, subscription, token generation and regeneration within WSO2 Governance Registry
  • Graphical differentiation view to compare two inter-related assets
  • New asset association UIs and extension point to perform add/remove associations based activities
  • Improved extension points to write tasks based on registry API and governance API

Updating service details

Service resources are stored within /governance/services. 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. 

 There are two ways to update the Governance Registry with service details as follows.

Using Governance Registry's UI

If you choose the first way and add a service bearing the name "OrderRegistration" with the namespace as, a resource will be created inside /governance/services/org/acme/services/OrderRegistration with application/vnd.wso2-service+xml as the media type. 

Uploading WSDL

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).

Community resources

WSO2 is willing to provide you guidance for any technical issues or questions regarding the Governance Registry product. You can communicate with the WSO2 Governance Registry development team directly using the relevant mailing lists mentioned here:

WSO2 encourages you to report issues and enhancement requests for WSO2 Governance Registry using the publicJIRA available at You can also track their resolutions and comment on the progress.

Questions regarding the Governance Registry can also be raised through Ensure that you tag the question with appropriate keywords such as WSO2 and Governance Registry so that our team can easily find your questions and provide answers.

For tutorials, articles, Webinars and similar resources, visit the WSO2 Library and search under the Resources menu.

Support options

WSO2 also offers a variety of development and production support programs, ranging from Web-based support during normal business hours, to premium 24x7 phone support. WSO2 is committed to ensuring that your enterprise middleware deployment is completely supported from evaluation to production. Our unique approach ensures that support leverages the open development methodology and is provided by the very same engineers who build the products. For additional support information please refer to  

  • No labels