Configuring different types of OMAG Servers¶
The configuration document controls that startup of services as an OMAG Server starts up. When you use the configuration commands from the Administration Services you are building up the properties in the configuration document.
The configuration document is divided into sections. Some sections contain properties that are needed by all types of servers and others are specialized for a particular type of server. The guides that follow show which services are relevant for each type of server and how to configure them.
- Metadata Access Store - this is a metadata server. It has a metadata repository and REST APIs to access and maintain the metadata. It may also send metadata change notifications over an event bus such as Apache Kafka and be a member of an open metadata repository cohort.
- Metadata Access Point - this is like a metadata access store in that it has REST APIs to access and maintain open metadata. It can also send metadata change notifications over an event bus. However, it must be a member of an open metadata repository cohort because it has no metadata repository of its own and relies on the other members o the cohort to supply it with metadata.
- Repository Proxy - this type of server hosts a connector that translates open metadata repository requests into calls to a third party metadata server. It is also able to convert metadata change events from the third party metadata server into open metadata change events.
- Conformance Test Server - this type of server is used by developers of the connectors that run in the repository proxy server. It tests that they are able to safely connect to an open metadata repository cohort.
- View Server - this server has specialist REST APIs for UIs and other non-Java environments, such as Python.
- Integration Daemon - this server hosts integration connectors that synchronize metadata between third party technologies and the open metadata ecosystem.
- Engine Host - this server hosts governance engines that monitor the open metadata ecosystem and take actions as requested/required.
- Lineage Warehouse - this server provides optimized access to lineage data. It has its own repository that it maintains by monitoring the open metadata ecosystem.
- Data Engine Proxy - this server supports a specialist connector for extracting metadata from IBM DataStage.
This is how these types of servers work together.