Configuration Document Sections¶

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. This guide takes you through each section of the configuration document and explains where it is relevant and how to configure it.

• The LocalServerId, LocalServerName, Local Server Type and Audit Trail properties are managed by Egeria and you do not need to configure them.
• The Event Bus Config is used to provide standard information about the event bus (typically Apache Kafka) that is used in each section that configures a service that is sending notifications over the event bus.
• The Basic Server Properties provides the standard properties of a server such as its user identifier and password.
• The Server Security Connection provides the information needed to enable fine-grained metadata authorization checks.
• The Repository Services defines the type of audit logging and metadata repository supported by the server. It also defines which open metadata repository cohorts that the server belongs to.
• The Access Services define which metadata APIs are activated in a metadata access server.
• The Engine Host Services define which governance engines are activated in an engine host server.
• The Integration Daemon Services define which integration connectors run in an integration daemon server.
• The View Services define which REST APIs are enabled in a view server.
• The Lineage Warehouse Services define the properties of the repository for a lineage warehouse server.
• The Data Engine Proxy Services define the properties of a data engine proxy server server.

Raise an issue or comment below