Connectors supporting the exchange and maintenance of metadata

These connectors help to accelerate the rollout of your open metadata ecosystem since they can be used to automate the extraction and distribution of metadata to the third party technologies.

Integration Connectors

The integration connectors support the exchange of metadata with third party technologies. This exchange may be inbound, outbound, synchronous, polling or event-driven.

Figure 1

Figure 1: Integration Connectors

Details of how integration connectors work is described in this article.

Files

The files integration connectors run in the Files Integrator Open Metadata Integration Service (OMIS) hosted in the Integration Daemon.

Databases

The database integration connectors run in the Database Integrator Open Metadata Integration Service (OMIS) hosted in the Integration Daemon.

Security Enforcement Engines

The security integration connectors run in the Security Integrator Open Metadata Integration Service (OMIS) hosted in the Integration Daemon.

Repository and Event Mapper Connectors

The repository connectors provide the ability to integrate a third party metadata repository into an open metadata repository cohort.

Figure 2 shows the repository connector providing a native open metadata repository that uses a particular type of store within an Egeria Metadata Server.

Figure 2

Figure 2: Repository connector supporting a native open metadata repository

Figure 3 shows the repository connector providing a native open metadata repository that uses a particular type of store within an Egeria Metadata Server.

Figure 3

Figure 3: Repository connector and optional event mapper supporting an adapter to a third party metadata catalog

The definition of the connector interfaces for these connectors is defined in the repository-services-api module in the org.odpi.openmetadata.repositoryservices.connectors.stores.metadatacollectionstore Java package.

Open Discovery Services

Open Discovery Services are connectors that analyze the content of resources in the digital landscape and create annotations that are attached to the resource’s Asset metadata element in the open metadata repositories in the form of an open discovery report.

Figure 4

Figure 4: Discovery Services

The interfaces used by a discovery service are defined in the Open Discovery Framework (ODF) along with a guide on how to write a discovery service.

The definition of the connector interfaces for discovery services is defined in the open-discovery-services module in the org.odpi.openmetadata.frameworks.discovery Java package.

Governance Action Services

Governance Action Services are connectors that perform monitoring of metadata changes, validation of metadata, triage of issues, assessment and/or remediation activities on request.

Figure 5

Figure 5: Governance Action Services

They run in the Governance Action Open Metadata Engine Service (OMES) hosted by the Engine Host OMAG Server.

The definition of the connector interfaces for governance action services is defined in the governance-action-framework module in the org.odpi.openmetadata.frameworks.governanceaction Java package.

Further information



License: CC BY 4.0, Copyright Contributors to the Egeria project.