Configuring Omni Gateway Configuration Caching in Connected Mode

To reduce scale-up time and increases resiliency, Omni Gateway can cache its gateway configuration in Redis shared storage. Omni replicas use the cached gateway configuration instead of each replica directly downloading the configuration from Anypoint Platform. By default, configuration caching is not enabled.

Omni Gateway configuration caching works by:

After the first Omni replica starts, the replica downloads the configuration from Anypoint Platform, encrypts the configuration, and stores it in Redis.
After subsequent replicas start, they use the locally cached configuration rather than downloading from Anypoint Platform.
If the Omni Gateway configuration changes on Anypoint Platform, the replicas download the necessary configuration from Anypoint Platform and store it in Redis for immediate use by the other replicas.

If caching is configured and Redis errors occur, each replica downloads configurations directly from Anypoint Platform. If Omni Gateway disconnects from Anypoint Platform, Omni Gateway uses the cached configuration until connections are restored.

Enable Omni Gateway Configuration Caching

Ensure the Redis shared storage is configured.

To learn more, see Configuring Shared Storage for Omni Gateway in Connected Mode.
Enable the FLEX_DATASOURCE_CONTROL_NODE_ENABLED=true environment variable.