Writing Configuration Document Store Connectors¶

The configuration store connectors contain the connector implementations that manage the storage of Configuration Documents for OMAG Servers.

There is one configuration document store connector defined for each OMAG Server Platform.

Configuration document store connector interface¶

The admin-services-api module provides the interface definition for this connector. Its interface is simple -- consisting of save, retrieve and delete operations:

/**
 * OMAGServerConfigStore provides the interface to the configuration for an OMAG Server.  This is accessed
 * through a connector.
 */
public interface OMAGServerConfigStore
{
    /**
     * Save the server configuration.
     * 
     * @param configuration configuration properties to save
     */
    void saveServerConfig(OMAGServerConfig   configuration);


    /**
     * Retrieve the configuration saved from a previous run of the server.
     *
     * @return server configuration
     */
    OMAGServerConfig  retrieveServerConfig();


    /**
     * Remove the server configuration.
     */
    void removeServerConfig();
}

The configuration document is represented by the OMAGServerConfig structure. The name of the server is stored in the localServerName property in OMAGServerConfig.

Sample implementations¶

The implementations of this connector provided by Egeria are found in the configuration-store-connectors module. There are two connectors:

• configuration-file-store-connector supports managing the open metadata configuration as a clear text JSON file.
• configuration-encrypted-file-store-connector supports managing the open metadata configuration as an encrypted JSON file.

Raise an issue or comment below