The Docker Compose deployment /volumes/ directory structure and contents

When deploying HCL Commerce 9.1.6.0 or greater with the Docker Compose method, the /volumes/ directory is used to mount storage into your deployment Docker images.

This process is implemented for two reasons:

For the ease of import of essential files into your Docker images, without the need to create or recreate custom images;
For HCL Commerce data to be persisted in the event that you turn off or restart your deployment.

The following table describes the /volumes/ directory structure.


Directory	File	Description
/volumes/		The root directory that contains all persisted directories can be mounted automatically within the provided HCL Commerce Docker containers.
/volumes/crs-app/certs/custom/		Contains any custom self-signed or third party SSL certificates files in JSON format for the `crs-app` container. See Managing certificates manually.
/volumes/store-web/certs/custom/		Contains any custom self-signed or third party SSL certificates files in JSON format for the `store-web` container. See Managing certificates manually.
/volumes/tooling-web/certs/custom/		Contains any custom self-signed or third party SSL certificates files in JSON format for the `tools-web` container. See Managing certificates manually.
/volumes/ts-app/certs/custom/		Contains any custom self-signed or third party SSL certificates files in JSON format for the `ts-app` container. See Managing certificates manually.
/volumes/ts-web/certs/custom/		Contains any custom self-signed or third party SSL certificates files in JSON format for the `ts-web` container. See Managing certificates manually.
/volumes/jdbc/		Contains the JDBC .jar files for database connections. Only required for Oracle databases. ojdbc8.jar
/volumes/elasticsearch/config/		Configuration volume mounted to Elasticsearch. Initially empty.
/volumes/elasticsearch/data/		Data volume mounted to Elasticsearch. Initially empty.
/volumes/redis/data/		Data volume mounted to Redis. Initially empty.
/volumes/zookeeper/data/		Data volume mounted to Zookeeper. Initially empty.
/volumes/hcl-cache-local-redis/
	cache_cfg-ext.yaml	The HCL Cache extension configuration file.
	redis_cfg.yaml	The HCL Cache Redis configuration file.
/volumes/hcl-cache-remote-redis/
	cache_cfg-ext.yaml	The HCL Cache extension configuration file.
	redis_cfg.yaml.template	The HCL Cache Redis configuration template file.
/volumes/googleAnalytics/		Contains the Google Analytics service file. See Adding the Service Account Credentials JSON to the Transaction Server.
/volumes/assets/auth/		Contains the assets that are created and used within the assets tool for the authoring environment. Typically this is a mounted NFS file system share.
/volumes/assets/live/		Contains the assets that are created and used within the assets tool for the live environment. Typically this is a mounted NFS file system share. This volume is required for both authoring and live environments to leverage the assets tool.
/volumes/ldap/		Contains deployment LDAP configuration.
	vmm.properties	The file containing your deployment LDAP configuration.
/volumes/approval-app/certs/custom/		Contains any custom self-signed SSL certificates for the Approval Server Docker container (`approval-app`) in JSON format. For more information, see Managing certificates manually.
/volumes/approval-app/boot-config/		Contains the configuration file for the Approval server (`approval-app`).
/volumes/postgresql/certs/		Contains the SSL certificates for secure communication with the PostgreSQL Database (`postgressql`) in PEM format.
	server.pem	The server certificate, in PEM format.
	key.pem	The private key of the server certificate, in PEM format.
/volumes/postgresql/docker-entrypoint-initdb.d/		Contains the script that is used to initialize the PostgreSQL Database that is used by the Approval server.
	init.sql	The SQL statements that are used to initialize the PostgreSQL Database.
/volumes/nextjs-store/certs/custom/		Contains any custom self-signed SSL certificates for the Ruby store container (`nextjs-store`) in JSON format. For more information, see Managing certificates manually.