A subsystem that is in development means that the Egeria community is still building the function. The code is added continuously in small pieces to help the review and socialization process. It may not run, or do something useful - it only promises not to break other function. There will be git issues describing the end state.
Governance Action Open Metadata Engine Services (OMES)¶
The Governance Action Open Metadata Engine Service (OMES) runs in an Engine Host OMAG Server.
It provides access to the open metadata ecosystem for governance action services. These are pluggable connectors that manage governance of open metadata. Their interfaces are defined by the Governance Action Framework (GAF) and supported by the Governance Action OMES.
The governance Action OMES also provides an API to allow a third party tool to validate that a specific governance action service will load in the engine host server, and it returns the usage information encoded in the service's implementation.
Using the Governance Action OMES¶
Governance action services are defined and linked to one or more governance action engines using the Governance Engine OMAS. The definitions for both the governance action engines and their linked services are stored in a metadata access server.
When the Governance Action OMES is configured in the engine host, a list of governance action engines is supplied. This determines which governance action engines and hence governance action services that it supports.
The Governance Action OMES is responsible for initializing the governance action engines and providing the context and runtime environment for governance action services when they are requested by third party technologies or through the governance action processing of the Governance Engine OMAS.