Skip to content
In development

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.

Archive Manager Open Metadata Engine Services (OMES)

The Archive Manager Open Metadata Engine Service (OMES) runs in an Engine Host OMAG Server. It hosts archive engines that consist of one or more related archive services.

Archive Manager OMES

It provides access to the open metadata ecosystem for the archive services through a context. Archive services are pluggable connectors that maintain open metadata archives based on the live metadata in the connected open metadata repositories.

The Archive Manager OMES also provides an API to allow a third party tool to validate that a specific archive service implementation will load in the engine host server, and it returns the usage information encoded in the service's implementation.

Using the Archive Manager OMES

Archive services are defined and linked to one or more archive engines using the Governance Engine OMAS. The definitions for both the archive engines and their linked services are stored in a metadata access server.

When the Archive Manager OMES is configured in the engine host, a list of archive engines is supplied. This determines which archive engines and hence archive services that it supports.

The Archive Manager OMES is responsible for initializing the archive engines and providing the context and runtime environment for the archive services when they are requested by third party technologies or through the governance action processing of the Governance Engine OMAS.

Back to top