Home
Documentation
HCL Commerce is a high-availability, highly scalable and customizable e-commerce platform. Able to support hundreds of thousands of transactions per day, HCL Commerce allows you to do business with consumers (B2C) or directly with businesses (B2B). HCL Commerce uses cloud friendly technology to make deployment and operation both easy and efficient. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels. Business users can also use AI enabled content management capabilities.
Reference
Topics in the Reference section contain all of the HCL Commerce reference documentation.
Docker container start up logic for HCL Commerce Version 9.1
When you deploy a container from an HCL provided image, an Entrypoint.sh helper script determines the configurations to use while starting up the container. Review the following information to learn about what the helper script does, and how you can customize the configurations.
Starting containers by retrieving parameters from Vault
You can use Vault (CONFIGURE_MODE=Vault) as a configuration management center and set your parameters in Vault. This method is best used in a multiple tenant environment by using an orchestration platform such as Kubernetes.
Starting Web server Docker container
Learn about how to start Web server Docker container by specifying CONFIGURE_MODE=Vault.

Starting Web server Docker container by retrieving parameters from Vault

Learn about how to start Web server Docker container by specifying CONFIGURE_MODE=Vault.

Mandatory parameters

These are the mandatory parameters that you need to specify to configure the container to retrieve more parameters from Vault. You can pass these parameters only as container environment variables.


Parameter name (key)	Value
TENANT	The name of the group that contains your set of environments. For example, `MyCompany`.
ENVIRONMENT	The name of the environment. For example, `Non-production`.
ENVTYPE	Then type of environment. For example, `auth`.
VAULT_TOKEN	The Vault token to use to connect to Vault and request certification from Vault PKI.
VAULT_URL	The Vault URL to use to connect to Vault and request certification from Vault PKI.

Optional parameters

These are optional parameters. You can pass these parameters as container environment variables, or you can store them in Vault. If you store the key-value pairs in Vault, the /SETUP/bin/vaultConfigure.sh script retrieves the values from Vault. All parameters that you specify as container environment variables take precedence over the values that are stored in Vault.


Parameter name (key)	Value
DOMAIN_NAME	The internal service domain name. The default value is : default.svc.cluster.local. If the deployed environment is on a special namespace on Kubernetes, the domain name should be `.svc.cluster.local`.
TX_HOST	The Transaction server hostname.
TX_PORT	The Transaction server port. Default value is 5443.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site.