ODPi Egeria Site organization
The Egeria content is organized across a number of repositories:
Egeria Core repository
The Egeria core repository contains the core Egeria functionality, and is organized into the following modules:
developer-resources - contains useful files and documentation for an Egeria developer.
open-metadata-conformance-suite - implementation of the tests that determine if a vendor or open source technology is compliant with the open metadata and governance standards.
open-metadata-distribution - contains scripts to extract the completed artifacts from the other modules and stores them together to make it easy to find them.
open-metadata-implementation - implementation of standards, frameworks and connectors.
- access-services - domain specific APIs known as the Open Metadata Access Services (OMAS).
- analytics-modeling - manage assets for an analytics platform.
- asset-catalog - search for assets.
- asset-consumer - create connectors to access assets.
- asset-lineage - provide lineage reporting.
- asset-manager - provide a synchronization interface for asset managers and catalogs.
- asset-owner - manage metadata and feedback for owned assets.
- community-profile - manage personal profiles and communities.
- data-engine - exchange metadata with a data processing engine.
- data-manager - exchange metadata with a technology that manages collections of data.
- data-privacy - support a data privacy officer.
- data-science - manage metadata for analytics.
- design-model - manage content from design models.
- dev-ops - manage metadata for a devOps pipeline.
- digital-architecture - support the definition of data standards and models.
- digital-service - manage metadata for a Digital Service.
- discovery-engine - manage metadata for metadata discovery services.
- glossary-view - search for glossary content.
- governance-engine - manage metadata for an operational governance engine.
- governance-program - set up and manage a governance program.
- it-infrastructure - manage metadata about deployed infrastructure.
- project-management - manage definitions of projects for metadata management and governance.
- security-manager - synchronization of metadata with security services.
- security-officer - set up rules to protect data.
- software-developer - deliver useful metadata to software developers.
- stewardship-action - manage metadata as part of a data steward’s work to improve the data landscape.
- subject-area - develop a definition of a subject area including glossary terms, reference data and rules.
- adapters - pluggable component implementations.
- authentication-plugins support extensions to technology such as LDAP that are used to verify the identity of an individual or service requesting access to data/metadata.
- open-connectors are connectors that support the Open Connector Framework (OCF).
- configuration-store-connectors contains the connectors that manage the open metadata configuration.
- connector-configuration-factory creates Connection objects to configure the open connectors.
- data-store-connectors contain OCF connectors to data stores on different data platforms.
- discovery-service-connectors contain ODF discovery service implementations.
- event-bus-connectors supports different event/messaging infrastructures. They can be plugged into the topic connectors from the access-service-connectors and repository-service-connectors.
- governance-action-connectors contains GAF governance action implementations.
- governance-daemon-connectors contains connectors for the governance daemon servers that monitor activity or synchronize metadata and configuration asynchronously between different tools.
- integration-connectors contains connectors synchronously exchanging between different third party technologies.
- repository-services-connectors contains connector implementations for each type of connector supported by the Open Metadata Repository Services (OMRS).
- audit-log-connectors supports different destinations for audit log messages.
- cohort-registry-store-connectors contains connectors that store the cohort membership details used and maintained by the cohort registry.
- open-metadata-archive-connectors contains connectors that can read and write open metadata archives.
- open-metadata-collection-store-connectors contains connectors that support mappings to different vendors’ metadata repositories.
- graph-repository-connector - provides a local repository that uses a graph store as its persistence store.
- inmemory-repository-connector - provides a local repository that is entirely in memory. It is useful for testing/developing OMASs and demos.
- omrs-rest-repository-connector - enables IBM Information Governance Catalog to support open metadata.
- rest-client-connectors contains connector implementations for issuing REST calls.
admin-services - supports the configuration of the OMAG Server Platform. This configuration determines which of the open metadata and governance services are active.
- common-services - support modules that are reused by other services.
- ffdc-services - provides base classes and validation for First Failure Data Capture (FFDC).
- generic-handlers - provides support for metadata management for open metadata types including visibility and authorization checking, anchor management and provenance recording.
- metadata-security - provides integration points for fine-grained security for metadata.
- multi-tenant - provides management of server instances within the OMAG Server Platform.
- ocf-metadata-management - provides metadata management for the Open Connector Framework (OCF) properties and APIs.
- repository-handler - provides an enhanced set of services for accessing metadata from the repository services.
- engine-services - services that host data management and governance engines. These run in the Engine Host OMAG Server.
- frameworks - frameworks that support pluggable components.
- audit-log-framework provides the interfaces and base implementations for components (called connectors) that access data-related assets. OCF connectors also provide detailed metadata about the assets they access.
- open-connector-framework provides the interfaces for diagnostics and exceptions.
- open-discovery-framework provides the interfaces and base implementations for components (called discovery services) that access data-related assets and extract characteristics about the data that can be stored in an open metadata repository.
- governance-action-framework provides the interfaces and base implementations for components (called governance actions) that take action to correct a situation that is harmful the data, or the organization in some way.
- governance-servers - servers and daemons to run open metadata and governance function.
- data-engine-proxy-services - supports automated metadata cataloguing from data engines.
- engine-host-services - supports the core function of the Engine Host OMAG Server.
- integration-daemon-services - supports the core function of the Integration Daemon OMAG Server.
- open-lineage-services - provides historic warehouse for lineage.
- integration-services - services that host integration connectors. These run in the Integration Daemon OMAG Server.
- api-integrator - services to catalog APIs supported by API Managers.
- catalog-integrator - services to exchange metadata with asset managers and catalogs.
- database-integrator - services to capture metadata from file systems and file management applications.
- files-integrator - services to exchange metadata with relational databases.
- organization-integrator - services to load metadata about the organization, including user identifiers, profiles, team structures and department hierarchy.
- lineage-integrator - services to load lineage metadata.
- security-integrator - services to push security tags to an external security enforcement point.
- topic-integrator - services to catalog topics and their event types from an Event Broker.
platform-services - the platform services support REST APIs for the OMAG Server Platform.
repository-services - metadata exchange and federation - aka the Open Metadata Repository Services (OMRS).
server-chassis - the server chassis provides the server framework for the OMAG Server Platform.
user-interfaces - browser based user interfaces.
- view-services - services that provide services for user interfaces. These run in the View Server OMAG Server.
- access-services - domain specific APIs known as the Open Metadata Access Services (OMAS).
open-metadata-publication - contains many of the general articles for Egeria’s website.
- open-metadata-resources - contains the open metadata demos and samples.
- open-metadata-archives - contains pre-canned collections of metadata for loading into an open metadata server.
- open-metadata-deployment - contains resources for deploying ODPi Egeria and related technology.
- open-metadata-labs - contains Jupyter Notebooks to guide you through using ODPi Egeria.
- open-metadata-samples - contains coding samples for Egeria APIs.
- open-metadata-tutorials - contains tutorials for managing your own ODPi Egeria environment.
- open-metadata-test - supports additional test cases beyond unit test.
Egeria connectors repositories
Egeria connectors repositories contain the code that allow non-Egeria technologies to connect into Egeria:
- Hadoop Ecosystem connectors houses the connectors for various Hadoop ecosystem components, like Apache Atlas and Apache Ranger.
- IBM Information Server connectors houses the connectors for IBM Information Server components, like Information Governance Catalog, DataStage and Information Analyzer.
- Database connectors
Egeria samples repository
The samples repository contains samples of using Egeria in various ways: Ansible roles, sample data and metadata, documented demonstrations, and so on at https://github.com/odpi/egeria-samples
License: CC BY 4.0, Copyright Contributors to the ODPi Egeria project.