The following governance concepts are described below.
...
WSO2 Governance Registry stores governance metadata and information on governance related entities. Registry resources storing this information and/or metadata are known as assets. Asset is a representation of any physical or digital entity that belong to an organization, which needs to be governed. In WSO2 Governance Registry, a set of predefined attributes compose an asset.
WSO2 Governance Registry provides an XML-based semantic structure called RXT (Registry Extension Types), to define the structure of a given asset type. There are two RXT categories as follows:
...
The WSO2 Governance Registry provides three extension points that provide a flexible, plug-in approach to link resources and to allow users you to encode their your own governance rules and policies. These include:
- "Handlers" - To Handlers: To implement custom behaviors to be applied to resources.
- "Filters": - To intercept standard behaviors to make room for custom behaviors; Filters determine which Handlers are to be engaged on a resource.
- "Aspects": - To associate custom behaviors with resources; Aspects differ form handlers, in that handlers are automatically applied to a resource, whereas, aspects are needed to be invoked manually through user action (for example, by clicking a button in the user interface).
There are the three key Registry features that exist at the top of the Repository. You can use these to provide your own customization on top of the base product.
Handlers are plug-able components that contain the custom processing logic for handling resources. Handler implementations provide alternative behavior for basic resource-related operations, by overwriting one or more methods in the Handler class.
Each Handler is associated with a Filter. Filters provide the criteria to engage with Handlers. The WSO2 Governance Registry always evaluates the associated Filter before invoking a Handler. If the Filter evaluates to true, it invokes its associated Handler.
Similar to Handlers, Aspects are used to associate custom behaviors with Resources. The difference between Aspects and Handlers is that, you automatically apply Handlers to a resource, whereas, you need to invoke Aspects manually through a user action (e.g. by clicking a button on the UI).
Additionally, with the enhanced WSO2 Governance Registry API, you can embed the Registry in a runtime system (for example, in e.g. in the Enterprise Service Bus), and support automated run-time governance. See For more information, see also Extensions.