Skip to content
In development

A subsystem that is in development means that the Egeria community is still building the function. The code is added continuously in small pieces to help the review and socialization process. It may not run, or do something useful - it only promises not to break other function. There will be git issues describing the end state.

Data Engine Open Metadata Access Service (OMAS)

The Data Engine OMAS provides APIs and events for data movement/processing engines to record the changes made to the data landscape.

It provides the ability to register the data engine itself along with the lineage details of the ETL transformations. Data Engine OMAS APIs offer support for creating the corresponding open metadata types for assets and jobs.

Using the Data Engine OMAS

Below is the list of tasks supported by Data Engine OMAS.

External Tool registration

Typically the first action to take for an external tool is to register as a software-server-capability.

External Tool lookup

An external tool can lookup for the registered external tool.

Create Schema Type

Create Port Implementation with schema type

Create Port Alias with delegation to a Port Implementation

Create Process, with corresponding Port Aliases, Port Implementations and Schema Types

Add lineage mappings to processes

Create Database

Create Relational Tables

Create Data Files

Delete Database

Delete Relational Tables

Delete Data Files

Delete Connections

Delete Endpoint

Sample use case

Initial load use case illustrates the integration between Data Engine OMAS and IBM's DataStage ETL tool.

Back to top