Configuration Service

Starting with Oracle GoldenGate 23ai, a new Configuration Service is available for managing the configuration files of Oracle GoldenGate for high availability (HA) purposes. A seperate ConfigService program within the Service Manager deployment, manages this service. The ConfigService manages configuration files from all deployments that are managed by this Service Manager. Configuration data includes:

• Microservices configuration data

• Parameter files

• Checkpoint data

• Database and user credentials

When you enable the ConfigService, this configuration data be stored seperately on another file system or a database as a backend, as shown in the following diagram.

Here are the features of the Configuration Service:

• The Configuration Service provides a REST API to all other processes with an Oracle GoldenGate installation to manage critical configuration data.

• Multiple Oracle GoldenGate installations can use the same highly-available Data Store.

  • The Configuration Data Store is managed independently of Oracle GoldenGate.

  • External applications can query configuration data independently of Oracle GoldenGate.

• Transparent failover and switching to a different server is supported.

  Consider a situation where two identical Oracle GoldenGate installations on different nodes use the Configuration Service to store configuration data externally in a database server for high availability. In case one of the installations experiences a failure, then using the failover mechanism, it automatically switches from one node to the other, and continues to use the Configuration Service to transmit and store configuration data to the database server.

• When you choose to use the Configuration Service, the configuration files are not stored in $OGG_ETC_HOME or $OGG_VAR_HOME directories.