InDev

Data Manager Open Metadata Access Service (OMAS)

The Data Manager OMAS provides APIs for technologies wishing to register new data assets, connections and related schema from data resources located in database servers, file systems, event brokers, API gateways and file managers and content managers.

The caller of this interface may be the data manager itself, or an integration daemon if the data manager does not support open metadata directly. The integration daemon calls the Data Manager OMAS client through the following integration services.

There are specific APIs for different types of data managers and assets. These reflect the terminology typically associated with the specific type of data manager to make it easier for people to map the Data Manager OMAS APIs and events to the actual technology. However, the specific implementation objects supported by these APIs all inherit from common open metadata types so it is possible to work with the resulting metadata in a technology agnostic manner using services such as the Asset Consumer OMAS.

The Data Manager OMAS APIs needs to accommodate slight variations between different vendor implementations of data managers, along with information relating to local deployment standards. As such there is provision in these interfaces to support:

Data Managers

The Data Manager OMAS Supports the following types of data managers:

Icon Name(s) Provenance Description
File System File System Local Cohort Instances Create metadata elements for files and folders along with their data connections and any known schema information. Catalogued files and folders are members of the local cohort because many different types of processes may work with them.
File Manager File Manager

Document Manager

Content Manager

Photo Library
External Instances Create metadata elements for files and folders along with their data connections and any known schema information. Catalogued files and folders are members of the data manager’s metadata collection because it is responsible for their maintenance.
Database System Database Server External Instances Create metadata elements for databases, database schemas, tables, views, columns, primary keys and foreign keys. Catalogued elements are members of the data manager’s metadata collection because it is responsible for their maintenance.
Event Manager Event Manager

Event Bus

Streaming Service
External Instances Create metadata elements for topics and the event payloads they support. Catalogued elements are members of the data manager’s metadata collection because it is responsible for their maintenance.
API Gateways API Gateway External Instances Create metadata elements for APIs and their supported headers and payloads. Catalogued elements are members of the data manager’s metadata collection because it is responsible for their maintenance.

Design information

The module structure for the Data Manager OMAS is as follows:


Return to the access-services module.


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