Open Metadata and Governance (OMAG) Subsystems¶
A subsystem is a collection of components within a software server that supports one or more related services. Subsystems can be organized in a hierarchy where course-grained subsystems can be decomposed into more fine-grained subsystems.
The OMAG Server is a flexible software server whose subsystems can be activated (or not) through the presence (or absence) of the subsystem's configuration properties in the OMAG Server's configuration document.
The potential subsystems within an OMAG Server are as follows:
- Open Metadata Repository Services (OMRS) for supporting access to metadata stored in metadata repositories and the exchange of metadata between repositories via an open metadata repository cohort. The repository services are further divided into OMRS subsystems that can be activated independently.
- Integration daemon services for running integration connectors that exchange metadata with third party technologies.
- Connected Asset Services for supporting the
ConnectedAssetinterface of a connector.
- Dynamically registered services provide specialist APIs for particular technologies and user roles. Each of these services runs in their own subsystem independent of the other registered services. The implementation may come from Egeria or a third party. The links are to Egeria provided dynamic services.
- Open Metadata Access Services (OMASs) for supporting domain-specific services for metadata access and governance. Access services run in the metadata access server.
- Open Metadata Engine Services (OMESs) for supporting specialized governance engines that drive governance activity in the open metadata ecosystem. The engine services run in the engine host server.
- Open Metadata Integration Services (OMISs) for supporting specific types of integration connectors. The integration services run in the integration daemon server.
- Open Metadata View Services (OMVSs) for supporting REST services for a User Interface (UI). The view services run in a view server.