THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Figure 1 shows the external APIs for the OMRS.
| 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). |
Figure 1: OMRS System Context Diagram
| |
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 4: Component Overview (level 2) |
The components are:
|
|
| ||
|
| |||
...