This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

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

What is new in this Release 

The WSO2 Governance Registry version 4.5.3 is the successor of version 4.5.2. It has several defect fixes and enhancements included in it. For a list of fixed defects in this release, refer to: WSO2 Governance Registry 4.5.3 - Fixed Issues. 

Enhancements:

  • New approval functionality added for lifecycle operations. For details, refer to Lifecycle Configuration Model.
  • Additional configuration options (Regex validations, Tooltips and Data field) are added to RXT Configuration Model.
  • RXT management is now facilitated through a simplified, web based user interface with RXT hot deployment capability.
  • Extended download facility to all governance artifacts with capability to download its dependent artifacts through a single point-and-click.
  • Multiple new operations introduced for the check-in client through the command-line.

Known Issues

Refer to the following link in WSO2 Oxygen Tank: WSO2 Governance Registry 4.5.3 - Known Issues.

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: http://wso2.org/mail .

WSO2 encourages you to report issues and enhancement requests for WSO2 Governance Registry using the publicJIRA available at https://wso2.org/jira/browse/REGISTRY. You can also track their resolutions and comment on the progress.

Questions regarding the Governance Registry can also be raised through http://stackoverflow.com. 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 Oxygen Tank and search under t he 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 http://wso2.com/support.  

  • No labels