0461 Governance Engines¶
The governance engine types in this model are used to create a governance engine definition.
A governance engine is a software capability that is able to run specific services on demand. These services, called governance services, typically implement specific logic that is needed to govern an organization's resources or the metadata associated with them.
Open metadata recognizes three types of governance engine:
- GovernanceActionEngine - Governance action engines and services support the active governance of metadata and the resources they represent. There are different types of governance action engines/services that are defined by the Governance Action Framework (GAF).
- OpenDiscoveryEngine - Discovery engines and services support the analysis of digital resources. The results of this analysis are stored in a discovery analysis report chained off of the corresponding Asset metadata element. The interfaces for discovery are found in the Open Discovery Framework (ODF). The types for the open discovery engines are shown on model .
- RepositoryGovernanceEngine - Repository governance engines and services support the maintenance of repository level concerns, such as monitoring audit logs and maintaining open metadata archives that are defined in the Open Metadata Repository Services (OMRS).
- EventActionEngine - event action engines and services support the automated management of context events and their associated actions. Note - this type of engine is still in development.
The capability of a governance engine is specified via the SupportedGovernanceService relationships.
requestType attribute in this relationship is the caller's request type (known as the governance request type). The
serviceRequestType attribute maps the governance request type to a request type supported by the associated governance service. If
serviceRequestType is null, the governance request type is used when calling the governance service.
Each governance request type linked to a specific governance engine must be unique.
requestParameters provide initial values of the request parameters passed to the governance services when it is called. These are overridden by any request parameters supplied by the caller.
Governance services are specialist connectors. They are represented in open metadata using the GovernanceService entity which is a specialization of DeployedConnector`. This entity is linked to a Connection entity via a ConnectionToAsset relationship.
A governance service can be linked to multiple governance engines via the SupportedGovernanceService relationship. It can be linked to the same governance engine multiple times as long as each SupportedGovernanceService relationship has a different governance request type.
The subtype of the governance service linked via the SupportedGovernanceService relationship should be consistent with the subtype of the associated governance engine. For example:
- A GovernanceActionService is linked to a GovernanceActionEngine.
- An OpenDiscoveryService is linked to an OpenDiscoveryService.
- A RepositoryGovernanceService is linked to a RepositoryGovernanceEngine.
- An EventActionService is linked to a EventActionEngine.
The Open Metadata Engine Services (OMES) support the implementation of each type of governance engine. They run in an Engine Host OMAG Server and draw their configuration from the GovernanceEngine and the linked GovernanceService elements in the associated metadata server.
The type definitions for discovery engines and services are shown in model 0601.
Raise an issue or comment below