The following governance concepts are described below.
...
Runtime governance comes into play, soon after the service is deployed. It monitors operational aspects of a service (service performance bottle necks, who is accessing more, etc.). Unlike design-time governance, most runtime governance functions are automated. Reports generated in this phase are important feedback, for the next service design and development iteration.
For more information on SOA Governance, see Registry Life-cycles and Forrester's Major SOA Requirements.
...
Registries and Repositories
...
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:
...
For more information on these assets, see Adding Assets.
...
Resources and Collections
...
The Registry supports configuring of dependencies and associations for resources. It automatically detects certain dependencies when you publish a resource. For example, a WSDL might use an external XSD that can be automatically detected and imported to the Registry. In addition to dependencies, the Registry provide a way to configure associations among resources. You are free to specify the type of association such as "contains" or "uses" during association configuration. These associations help figure out the possible relationships that may exist among resources and also in analyzing the impact on changing a resource. See also Managing Dependencies and Associations.
...
API management
Subscriptions management
Notifications
Monitoring
...
Services (SOAP or REST) in WSO2 G-Reg are implemented as configurable governance artifacts (RXT files), which you create using the G-Reg Publisher. Usually, in WSO2 APIM service publication is done using the APIM Publisher Web interface. Instead, you can integrate WSO2 APIM with WSO2 G-Reg, to directly publish APIs to APIM Publisher using the services deployed in the WSO2 Governance Registry. For more information on API management, see Integrating with an External WSO2 API Manager.
...
Subscriptions and notifications
The notifications feature can be used to generate notifications for events that occur as a result of performing operations. To receive notifications, create a subscription to a particular event along with a specified notification method (e-mail alert or G-Reg Publisher/Store notification). For more information on subscriptions and notifications, see Adding Subscription Notifications in Publisher and Store.
...
Extensibility
The WSO2 Governance Registry provides three extension points that provide a flexible, plug-in approach to link resources and to allow you to encode your own governance rules and policies. These include:
- 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 (e.g. in the Enterprise Service Bus), and support automated run-time governance. For more information, see also Extensions.