THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Open Metadata and Governance technology needs to be packaged in a flexible structure to allow different metadata tools, engines and repositories to be integrated together in a range of deployment patterns that range for simple projects to large multi-country, cross enterprise metadata support. The packages are summarized in the table below.
| Package Name | Description and Usage | Contents |
|---|---|---|
| Open Metadata and Governance Client | Provides Java classes that call the Open Metadata Access Services (OMAS) REST APIs (requires the IP address and port number of the deployed OMASs). This package supports the Caller Integration Pattern. It is used by data platforms, engines, tools and applications to integrate with an independently deployed open metadata repository (or open metadata repository cluster). | OMAS java client libraries |
| Open Metadata and Governance Metadata Highway | Provides the metadata cluster registry and event management mechanisms for an open metadata repository cluster that can run independently of a specific metadata repository. It is used by an organization that already has a number of established metadata repositories and wishes to connect them together into an open metadata repository cluster. | |
| Open Metadata and Governance Repository Stack | Provides a metadata repository, open metadata type system, Open Metadata Access Services (OMASs) for tools, engines, data platforms and applications to create, retrieve and update metadata plus the Open Metadata Repository Services (OMRS). The OMRS includes the capability to join an open metadata repository cluster and to (optionally) provide the OMRS Cluster Registry capability. This package supports the Native Integration Pattern. | |
| Open Metadata and Governance Repository Proxy | Provides an OMRS Repository Proxy toolkit for deploying OMRS Connectors into the open metadata and governance ecosystem. It is used when there are metadata repositories in the open metadata repository cluster that do not have these OMRS Connectors included locally in their build and need to access them through a remote call. | |
| Open Metadata and Governance Access APIs | Provides a deployment package of all the Open Metadata Access Services (OMAS) REST APIs and OMRS Connectors included in the Apache Atlas code base. | |
| Open Metadata and Governance Adapter Toolkit | Provides the API and libraries for integrating an existing metadata repository into the open metadata and governance ecosystem. This includes the APIs for an OMRS Connector and design guidance for building an Event Mapper component. This package is for organizations that are implementing the Adapter Integration Pattern. | |
| Open Metadata and Governance Discovery Toolkit | Provides the development APIs and libraries for building open discovery services. It also includes the open discovery framework and server for running the open discovery services along with the Discovery OMAS client. This package is used for organizations that are using the Plug-in Integration Pattern for metadata discovery. | Open Discovery Framework (ODF) and Server Discovery OMAS Client |
| Open Metadata and Governance Stewardship Toolkit | Provides a tool kit for automating the management of exceptions and logs from the Governance Action Framework (GAF). It is used by an organization that has one or more open metadata repositories deployed and wishes to built out their operational governance capability. This package includes the APIs and samples, plus notification and workflow capability to enable the detection of situations that need action, the implementation of rules and actions that can be automated, plus support for human intervention and approval. This package is used for organizations that are using the Plug-in Integration Pattern for automating governance. | TBD. Governance Engine OMAS client |
| Open Metadata and Governance Connector Toolkit | Provides a toolkit for developers to build connectors to data and related assets. It includes the APIs for the connectors and some sample connectors to act as a pattern as well as guidance on building connectors. Connectors are dependent on the Connected Asset Open Metadata Access Service (OMAS). This package does not include a metadata repository and so it needs the server IP address and port number of the deployed OMAS APIs that are connected to a compliant open metadata repository in order to test the connectors metadata interfaces. This package is used for organizations that are using the Plug-in Integration Pattern for new connectors. | Open Connector Framework (OCF) interfaces and sample connectors. |
| Open Metadata and Governance Full Platform | All of the components from Apache Atlas. Used by an organization that wishes to exploit the open metadata and governance capability for multiple use cases and wishes to evaluate/consume all parts of the capability. | Everything |