Building Container Images
The Self-Managed Commerce containerization relies on the build and deployment of the following commerce service container images.
| Image Name | Description |
|---|---|
| cortex | The Commerce API and Cortex Studio applications installed on the tomcat image. |
| search | The Search application, used for Search Primary and Search Secondary services, installed on the tomcat image. |
| cm | The Commerce Manager applications installed on the tomcat image. |
| batch | The Batch Server applications installed on the tomcat image. |
| integration | The Integration Server applications installed on the tomcat image. |
| data-sync | The Data Sync WebApp applications installed on the tomcat image. |
| mock | The Wiremock service applications installed on the tomcat image. |
| data-pop-tool | The Commerce Data Population tool and Java SDK installed on the amazonlinux_java image. |
| activemq | Java Messaging Service (JMS) for Commerce environments installed on the amazonlinux_java image. |
| mysql | A containerized database option suitable for transient Self-Managed Commerce environments. |
At a very high level, three steps are required to build the container images:
- Build the base images.
- Build the Commerce artifacts.
- Build the Commerce images.
Each build step creates different artifacts. For more information about the relationship between these artifacts, see Self-Managed Commerce Deployment Artifacts.
Identify image tagging strategies suitable for your business and team workflows to ensure that the right versions of the images are used in the right environments.
Regularly rebuild and deploy the images to obtain and apply operating system updates and patches.
Self-Managed Commerce Build Tools
New and redesigned build tools are available with the most recent releases of Self-Managed Commerce, under the devops/build_tools folder of the Self-Managed Commerce ep-commerce Git repository. Container images created by these tools are equivalent to and compatible with images built by the previous Elastic Path Docker tools. These tools are recommended for customers creating or updating Self-Managed Commerce continuous integration (CI) or build solutions.
For an introduction to the build tools, and the steps to build the container images, see Build Tools Overview.
Previous tools
The previous generation of Self-Managed Commerce image build tools, called Elastic Path Docker, remain available. Container images created by the newer build tools are equivalent to and compatible with images built by the older Elastic Path Docker tools.
The BaseImageBuilder.sh script is provided to build the amazonlinux-java and tomcat images. The ActiveMqImageBuilder.sh script is provided to build the activemq image. The EpDbImageBuilder.sh script is provided to build the mysql image.