configuration

Starting with 9.1, the provider is automatically deployed and enabled in all containers, and the default caches are configured to use s. This section describes the configurations that can be used with s.

HCL Cache configuration

Important: When deploying with Kubernetes, cache configuration is made within the Helm charts. For more information, see Helm support.

The uses three main configuration files in YAML format:


Configuration file	File location	Description
Default configuration file	/SETUP/hcl-cache/cache_cfg.yaml	The default configuration file contains provided (out-of-the-box) cache configurations.
Custom configuration file	/SETUP/hcl-cache/cache_cfg-ext.yaml	Settings in the custom configuration file, which shares the same format as the default configuration file, override settings in the default configuration file. Use this file to make customizations to your configuration.
Redis connection configuration file	Customizable location. Defaults to: /SETUP/hcl-cache/redis_cfg.yaml	The uses the Redisson Reds client to interface with the Redis server. Redisson supports multiple Redis server topologies, including standalone, master-subordinate and clustering. The configuration of the connection, including options such as timeouts, SSL and authentication is stored in this configuration file.

Helm support

When installing with Helm support, the configurations are stored in a config map that is automatically mounted on the containers. The configurations to be stored in the config map can be customized in values.yaml prior to installation, or by updating the config map contents after installation.

If the config map is updated, running pods need to be restarted to load the updated configurations.

To use a password with the Redis connection, add the password element to the Redis connection configuration under the redis_cfg.yaml element in the hcl-cache-config configuration map. The Redis password can be stored encrypted in Vault.

Create a Vault key "redisPasswordEncrypt" under the environment type (for example qa or prod). Store its encrypted value. The encrypted value can be obtained by running the wcs_encrypt.sh utility from inside the utility container. For more information, see Generating encrypted data with the wcs_encrypt utility
Set the password in the hcl-cache-config configuration map as follows:
```
 password: "${JNDI/ENCRYPTED:REDIS_PASSWORD_ENCRYPT:-}"
```
The containers will automatically load the redisPasswordEncrypt Vault key and map it to a JNDI entry for the Redis client to use. For more information, see the hclCache and configMap sections within the values.yaml configuration file.

Cache provider configuration

While is the default cache provider for all default (out-of-the-box) caches, the caching configuration of and can be modified to use the DynaCache provider, or the WebSphere Extreme Scale DynaCache provider.

For more information, see Setting cache providers in HCL Commerce.