THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- OMRS Repository Connectors - providing a common interface to metadata repositories.
- OMRS Audit Log Store - providing a common interface to an audit log destination.
- OMRS Cohort Registry Store - providing a common interface to the cohort registry store that saves information about members of a cohort.
- OMRS Archive Store - providing a common interface to Open Metadata Archives
- OMRS Topic Connector - providing a common interface to an instance of the OMRS Topic.
- OMRS Repository Event Mapper - providing a common API for specific implementations of OMRS Event Mappers to implement
...
OMRS Repository Connector Implementations
...
| Connector | Description | JIRA | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Local Atlas OMRS Repository Connector | This is the connector to a local Apache Atlas metadata repository. It calls directly to Apache Atlas's internal interface for the metadata repository and as such is always deployed in an Apache Atlas Server. |
| ||||||||
| OMRS REST Repository Connector | This is a connector to a remote Apache Atlas repository (or any other metadata repository that supports the OMRS REST APIs). This is the connector used by an open metadata repository to make a direct call to another open metadata repository. It is also used by the Enterprise OMRS Connector described below. |
| ||||||||
| IGC OMRS Repository Connector | This is the connector for retrieving metadata from IBM’s Information Governance Catalog. This connector translates the calls to its OMRS Connector API to IGC's REST API and then translates the results of these calls to appropriate responses on its API. |
| ||||||||
| Enterprise OMRS Repository Connector | This connector can issue calls to multiple OMRS connectors and aggregate the results as if the metadata was stored in a single repository. This is how metadata queries are federated across the metadata repository cohort. Since all implementations of OMRS connectors have the same API, the Enterprise OMRS Connector is able to work will a heterogeneous collection of OMRS connectors. It uses its configuration to create the appropriate instances of the OMRS connectors. |
|
...
Figure 1: OMRS Connector Patterns | A | The Local Atlas OMRS Connector is hosted in the Apache Atlas server and calls the local internal metadata repository API. Every Atlas server will have one of these connectors. |
| B | The OMRS REST Connector translates calls to its interface to calls the OMRS REST API of a remote metadata repository. Apache Atlas servers support the OMRS REST API, and other Open Metadata native metadata repositories may also implement this interface too. | |
| C | Metadata repositories that have their own API can create a connector to translate OMRS calls to call to their API. The IGC OMRS Repository Connector is an example of this type OMRS connector written to support a specific metadata repository that is not Apache Atlas. This OMRS Connector will be included in the Apache Atlas build so it can be called directly from and OMAS API, the Enterprise OMRS Connector or the OMAG Repository Proxy. | |
| D | The Enterprise OMRS Connector (see here for more details) converts each call to its interface to a call to each of the OMRS connectors that it is configured to work with. It then aggregates the results together for form the response to its call. |
...