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

In organizations, people engage with the Governance system in various ways based on their roles and responsibilities. Also, they have varied expectations from the Governance system. WSO2 Governance Registry 5.X series is designed by standardizing these user groups to provide a highly specialized portal experience on the Governance system for each user group. 

The architecture of WSO2 Governance Registry (G-Reg) is described in the following sections.

User groups

Following are the standard user groups of WSO2 Governance Registry and the portals that they interact with.

User groupDescriptionPortal
consumer A consumer is a user who looks for assets (such as services), and related artifacts to consume them.Governance Store
governor A governor is a user who populates the Registry with assets, and uses the Registry to govern them (i.e. document, manage the lifecycle, define relationships across artifacts etc.)

Governance Publisher


administrator

An administrator is a user who is responsible to administrate the whole system (i.e. introduce new asset types, remove existing asset types, introduce new lifecycles, remove or modify existing lifecycles, and add/remove users and roles etc.)Management Console

agent

An agent is another system, which interacts with WSO2 Governance registry in a remote manner.SOAP/REST/Java APIs/Checkin Client

High level architecture

The following diagram depicts the high level architecture of WSO2 Governance Registry. It is composed of the following two main components.

  • Governance Framework
  • Registry

Governance Registry achitecture diagram

Governance Framework

Governance Framework simplifies the internal Registry-level implementations in managing Resources for Governance Framework users. The following diagram illustrates possible approaches to interact with the Governance Framework.

Governance Framework diagram

The Governance Framework consists of the following three main Web based user interfaces to facilitate the features and functionality. 

WSO2 G-Reg Publisher

WSO2 G-Reg Publisher provides an end-user, collaborative web interface for governance asset providers to publish artifacts, manage them, show their dependencies, and gather feedback on quality and usage of them. It is powered by WSO2 Enterprise Store (WSO2 ES). For more information on WSO2 G-Reg Publisher and its functionality, see Publisher Guide.

WSO2 G-Reg Publisher

WSO2 G-Reg Store

WSO2 G-Reg Store provides an end-user, collaborative web interface for consumers to self-register, discover governance artifact functionality, subscribe to artifacts, evaluate them and interact with artifact publishers. It is enriched with one level of categorization, and a tag cloud based filtering capabilities. It is powered by WSO2 Enterprise Store (WSO2 ES). For more information on WSO2 G-Reg Store and its functionality, see Store Guide.

WSO2 G-Reg Store

WSO2 G-Reg Management Console

The Management console of WSO2 G-Reg is a Web-based user interface that allows administrators to configure, monitor, tune, and maintain WSO2 Governance Registry. For more information on the Management Console and its functionality, see Product Administration Guide.

Management Console of WSO2 G-Reg

Registry Core

Following diagram illustrates possible approaches to interact with the Registry.

Registry diagram

The Registry API provides a programming interface to the Registry Core, which lays the foundation for extension APIs such as the JCR 2.0 API. At the heart of the Registry Core lies the Repository, fronted by a Data Access Layer through which, the data is stored and fetched on a JDBC compliant RDBMS. In addition to fixed SQL queries, WSO2 Governance Registry also supports execution of customized SQL queries. WSO2 G-Reg support a wide-variety of DBMSs as follows.

  • IBM DB2
  • Apache Derby (Embedded and Remote)
  • H2 (Local and Remote)
  • Microsoft SQL Server (and Express Editions)
  • OpenEdge
  • Oracle 10g/11g
  • MySQL
  • PostgreSQL

For more information, see Working with Databases.

  • No labels