Starting containers with default configurations

Learn how to start the containers with the default configurations. That is without specifying the CONFIGURE_MODE parameter. There are mandatory and optional parameters that you can specify depending on how you want to start your container.

Use the default mode in the following scenarios:
  • You only want to view files inside the container and do not need the container to connect and communicate with other containers.
  • Your Docker environment (database and other containers) all use the HCL default values for passwords and container host names. If you do not use the default host names and passwords, do not use this method. Your containers will not function properly.
  • You are deploying HCL Commerce locally as an individual test environment.
Note: This configuration mode is ideal for using Docker Compose. You can leverage the service name or network alias to ensure that the service names are the same as the default host names. You can specify the mandatory and optional parameters as environment: parameters in the Compose file. For examples on how to start HCL Commerce by using Docker Compose, see Deploying HCL Commerce Version 9.1 with Docker Compose (for non-production usage).
To start the container with default configurations to view files inside the container, use:
docker run -it -e LICENSE=accept image
  • The default host names for all containers.
    Docker image Default host name
    commerce/crs-app store
    commerce/search-app search
    commerce/xc-app xc
    commerce/ts-app app
    commerce/ts-web web
    commerce/ts-db
    Note: This assumes that you are running a Db2 Docker container.
    db
    commerce/tooling-web tooling-web
    commerce/store-web store-web
    HCL Commerce Version 9.1.9.0 or latercommerce/graphql-app graphql
    commerce/search-nifi-app nifi
    commerce/search-query-app
    • query for the store query service
    • data-query for the business query service
    commerce/search-registry-app registry
    commerce/search-ingest-app ingest
    docker.elastic.co/elasticsearch/elasticsearch elasticsearch
    bitnami/zookeeper zookeeper
    HCL Commerce Version 9.1.3.0 or laterredis redis
  • The default SubjectAlternativeName in container certification.
    [DNS:*, DNS:app, DNS:web, DNS:search, DNS:store, DNS:tooling-web, DNS:store-web, DNS:query, DNS:data-query, DNS:ingest, DNS:nifi, DNS:registry, DNS:elasticsearch, DNS:zookeeper, DNS:localhost, DNS:search_master, DNS:search_repeater, DNS:search_slave, DNS:cache-app, DNS:graphql, DNS:prerender, DNS:mustgather]
  • The default datasource credentials.
    Database parameters Value
    Database type (DBTYPE) DB2db2 Oracleoracle
    Database instance name (DBNAME) mall
    Database user (DBUSER) wcs
    Database user password (DPUSERPW) wcs1
    Database host (DBHOST) db
    Database port (DBPORT) DB250000 Oracle1521
    Database administrator (dbadmin) db2inst1

Creating HCL Commerce containers with docker run

If your environment satisfies the default conditions, you can run the following command:
docker run -it -e LICENSE=accept  \
    -e <Parameter1>=<Value1>
    -e <Parameter2>=<Value2>
    ....
    <Docker Image>

Creating HCL Commerce containers with docker compose

If you are using Docker Compose, ensure that you specify these parameters as environment: variables in your compose file.