Configuration Service

Starting with Oracle GoldenGate 26ai, a new Configuration Service is available for managing the configuration files of Oracle GoldenGate. The Configuration Service provides an alternate method for storing checkpoint and recovery information. This alternate method uses a database repository instead of the file system. A seperate ConfigService program within the Service Manager deployment, manages this service.

Note: The Configuration Service is only available with Oracle database on Linux.

After the ConfigService is installed, it cannot be removed.

Note: Use of the ConfigService should only be done if using the new HA Cluster functionality that is not yet released.

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.

Configuration Service used to store configuration data for all Oracle GoldenGate process. Configuration data can be stored in Filesystem or Oracle Database in the backend.

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 Data Store.
- The Configuration Data Store is managed independently of Oracle GoldenGate.
- External applications can query configuration data independently of Oracle GoldenGate.
When you choose to use the Configuration Service, the configuration files are not stored in $OGG_ETC_HOME or $OGG_VAR_HOME directories.