Open Metadata Repository Services (OMRS) Overview
Figure 1 shows the external APIs for the OMRS.
Figure 1: OMRS System Context Diagram
On the left hand side is the administration interface supported by the OMAG server. This is where configuration is passed to the OMRS, and status and other relevant information is made available to the OMAG Administration Services.
Along the top is the interface with the Open Metadata Access Services (OMAS). The OMRS provides access to the open metadata repositories through both a call API (see Enterprise OMRS Repository Connector) and an event topic (see Enterprise OMRS Topic).
Along the bottom are the six types of connectors that provide the OMRS with access to the stores and system resources it needs to support the OMAS.
These connectors enable the OMRS to be deployed into different types of server environments and connect with different types of infrastructure and services.
Repository connectors provide a common interface for metadata repositories. The OMRS store connectors can range from simple file stores to enterprise / cloud provider admin repositories and the event topic can support different types of messaging infrastructure.
Inside the OMRS are 4 major subsystems (groups of components):
Figure 2: Component Overview (level 1)
Enterprise Repository Services provides a virtual metadata repository by combining the content of multiple open metadata repositories and delivering this metadata through a single API and event topic. The Enterprise Repository Services provide the enterprise access metadata support for the OMASs.
- Administration Services drive the
initialization of the OMRS at server startup, provide access to the OMRS’s internal status and
coordinate the orderly termination of OMRS when the open metadata services
are deactivated. OMRS’s administration services are called by the server’s administration
services. It is supplied with configuration information including:
- Connections for the connectors it should use.
- Information about the local repository (if any).
- Whether the enterprise repository services should be initialized.
- Details of any cohorts it should join.
Cohort Services manage the local server’s membership in one or more open metadata repository cohorts.
- Local Repository Services manage the local server’s open metadata repository.
The OMRS is highly configurable. The figures below show the different combinations. Figure 3 shows the OMRS supporting the OMASs with access to a single, local-only repository - with no connectivity to other open metadata repositories.
Figure 3: Local only
Figure 4 shows the OMRS supporting a server with no local repository - so that all metadata for the OMASs is coming through the cohort services from remote metadata repositories. This is the caller integration pattern.
Figure 4: Access services
Figure 5 shows OMRS supporting a simple repository proxy server. The OMASs are not deployed and the local repository is configured to connect as an adapter for a non-native open metadata repository. The cohort services connect this metadata repository with other members in one or more cohorts. This is called the adapter integration pattern.
Figure 5: Repository proxy
Figure 6 shows all of the OMRS components in operation, supporting the OMASs with a local repository and connectivity to other repositories through the cohort servers.
Figure 6: Complete
The different combinations of operation required means that the OMRS components need to be flexible and communicate with one another through well-defined interfaces so that component implementations can be swapped in and out to support different configurations.
Figure 7 shows the main components of OMRS within each subsystem.
Figure 7: Component Overview (level 2)
License: CC BY 4.0, Copyright Contributors to the ODPi Egeria project.