Figure 1 shows the external APIs for the OMRS.
Figure 1: OMRS System Context Diagram |
On the left hand side is the administration interface used 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. The OMRS provides access to the open metadata repositories through both a call API (see Enterprise OMRS Repository Connector) and an event topic (see Federated 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. The 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 files stores to enterprise / cloud provider admin repositories and the event topic can support different types of messaging infrastructure. |
Inside the OMRS are 4 major groups of components: Enterprise Repository Services, Administration Services, Cohort Services and Local Repository Services
Figure 2: Component Overview (level 1) |
|
The OMRS is highly configurable to support the different OMAG Server Roles. Figure 3 below shows the different combinations:
OMRS supporting the OMASs with access to a single, local only server - with no connectivity to other open metadata repositories. | 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. |
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. | This final picture shows all of the components in operation, supporting the OMASs with a local repository and connectivity to other repositories through the cohort servers. |
Figure 3: Different combinations of OMRS components to enable different OMAG Server roles |
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 4 shows the main components of OMRS.
Figure 4: Component Overview (level 2) |
The components are:
|
|
| ||
|
|