Open Metadata Engine Services (OMES)¶
The engine services run in the engine host. They provide the special services that are available to the governance services through their context. There is an engine service for each type of governance service. Each engine service also maps the calls from the governance service to calls to the services of a metadata access server. The table below summarizes the engine services, the type of governance service they support and the service on the metadata access server that they call.
| Name of the Engine Service | Type of Governance Service supported | Partner service in the metadata |
|---|---|---|
| Survey Action OMES | Survey Action Service | Asset Owner OMAS |
| Governance Action OMES | Governance Action Service | Governance Server OMAS |
| Context Event OMES | Context Event Service | Stewardship Action OMAS |
| Repository Governance OMES | Repository Governance Service | Repository Governance OMAS |
The diagram below shows the generic picture of an engine service plugged into the Engine Host. The engine host services provide most of the capability of the Engine Host. This includes managing the retrieval of the governance engine definitions from the metadata access server that map the engine action requests to calls to the governance services.
The engine services each provide an implementation of the governance engine handler that is able to run a particular type of governance service. When an engine action is initiated, the engine host services receives it, claims it, selects the right engine handler and passes the engine action to it. The governance engine handler runs the governance service through its governance service handler, making calls to the partner service as required. It records the outcome in the engine outcome in the metadata access server.
Raise an issue or comment below