Technical preview function is in a state that it can be tried. The development is complete, there is documentation and there are samples, tutorials and hands-on labs as appropriate.
The community is looking for feedback on the function before declaring it stable. This feedback may result in changes to the external interfaces.
Engine host services¶
The engine host services support the behavior of the engine host OMAG Server. They manage the start up and shutdown of the configured Open Metadata Engine Services (OMESs) as well as retrieve the configuration of their governance engines and governance services through the Governance Engine OMAS running in a Metadata Access Server.
The engine host services also provide a REST API to query the status of the governance engines running in the server.
The internals of the Engine Host OMAG Server are shown in Figure 1:
Figure 1: Inside the Engine Host OMAG Server
The engine host services shown at the top of the diagram are responsible for:
- Starting up each of the configured OMESs for the engine host.
- Retrieving the configuration for each governance engine and its governance services configured within the OMESs using the Governance Engine OMAS.
- Initializing an appropriate governance engine handler (implemented by the OMES) for each retrieved governance engine configuration.
- Listening for governance action requests and passing each one to the appropriate governance engine handler for the governance engine that supports the request type.
- Monitor changes in the governance engine configuration and passing them on to the corresponding governance engine handler so the OMESs have the latest configuration.
There is more of an overview of open governance in the Governance Action Framework (GAF).
Instructions for defining Governance Engines and Governance Services are located under the Discovery and Stewardship feature.
Raise an issue or comment below