Setting the spiuser password in your Docker images
An administrator needs to choose a password for a default SPI user that is named spiuser, and then set the spiuser password in the HCL Commerce Docker containers.
This password is used for inter-component server API invocation only.
This password is stored for the Store server, Search server and Customization server within the WebSphere Application Server V8.5.5 Liberty userregistry.xml configuration file. In the Transaction server, the spiuser user is configured in the database.
The password must be the same on all servers, and each Docker image must be configured with the correct spiuser user password. If the passwords do not match, or if a container is left unconfigured, then the component servers cannot make the required API calls to function together.
- The Store server calls the Search server and Transaction server.
- The Customization server calls the Transaction server.
- The Transaction server calls the Customization server.
- The Search server calls the Transaction server, Customization server, and other Search servers.
- Ensure that you use a secure password.
- A minimum 45 character length requirement was introduced for new deployments of HCL Commerce 9.1.9.0 or greater.
Procedure
-
Log on to the dedicated server that is hosting the Utility server Docker container.
If a Utility server Docker container is not deployed, see Preparing a Docker host server to launch Utility server Docker container.
-
Enter the Utility server Docker container.
For example,
docker exec -it utility_container_name bash
- Go to the /opt/WebSphere/CommerceServer90/bin directory.
-
Run the following command to encrypt the spiuser password.
./wcs_encrypt.sh plain_text_spiuser_password
-
Copy and save the plain_text_spiuser_password within a text
file.
You require the plain text password to deploy the HCL Commerce containers.
- Generate the merchantKey encrypted password, and store it in the database.
- Exit the Docker container.
-
Share the plain text spiuser password with your development team.
Note: Developers need to use the plain text password when they load the HCL Commerce schema to the database. Particularly, developers need to provide the spiuser password when Loading the HCL Commerce database schema.