A component 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. Expect to find git issues describing the end state.
Repository Governance Open Metadata Engine Services (OMES)¶
The Repository Governance Open Metadata Engine Service (OMES) runs in an Engine Host OMAG Server. It hosts repository governance engines that consist of one or more related repository governance services. Governance repository services are pluggable connectors that perform repository governance services such as maintain open metadata archives based on the live metadata in the connected open metadata repositories.
The Repository Governance OMES provides access to the open metadata ecosystem for the repository governance services through a context. It also provides an API to allow a third party tool to validate that a specific repository governance service implementation will load in the engine host server, and it returns the usage information encoded in the service's implementation.
Using the Repository Governance OMES¶
The definitions for both the repository governance engines and their linked services are stored in a governance engine definition. The governance metadata definitions are loaded as metadata into the open metadata ecosystem.
When the Repository Governance OMES is configured in the engine host, a list of repository governance engine names is supplied. These names are used to retrieve the governance engine definitions for the archive engines in order to configure the Repository Governance OMES.
The Repository Governance OMES is responsible for initializing the repository governance engines and providing the context and runtime environment for the repository services when they are requested through the [engine action](/concepts/engine-action processing of the Governance Engine OMAS.
Raise an issue or comment below