Configuring Omni Gateway Configuration Caching in Connected Mode
To reduce scale-up time and increase resiliency, Omni Gateway can cache its gateway configuration in 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 shared storage.
-
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 shared storage for immediate use by the other replicas.
If caching is configured and shared storage 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.
| When using distributed shared storage, cached configurations are lost when all replicas go down (Managed Gateway is stopped or self-managed is scaled to zero replicas). For persistent caching, use Redis shared storage. |
Enable Omni Gateway Configuration Caching
-
Make sure shared storage is configured.
Configure either:
-
Distributed shared storage: Cached configurations are lost when all replicas go down
-
Redis shared storage: Cached configurations persist when all replicas go down
-
-
Enable the
FLEX_DATASOURCE_CONTROL_NODE_ENABLED=trueenvironment variable.