Building Container Images
At a very high level, three steps are required to build the Self Managed Commerce container images:
- Build the Commerce deployment package.
- Build the base images.
- Build the Commerce images.
Each build step creates different artifacts. For more information about the relationship between these artifacts, see Elastic Path Commerce Deployment Artifacts.
important
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.
important
Regularly rebuild the images to obtain and apply operating system updates and patches.
Building the Deployment Package
The Commerce deployment package is created by running a Maven build process against the Commerce source code. For more information, see Build Deployment Package.
Building the Base Images
The following table shows the container images generated by base image build options.
| Image Name | Description |
|---|---|
| amazonlinux | The Amazon Linux operating system |
| amazonlinux-java | An image with the Java SDK installed on Amazon Linux |
| tomcat | The Apache Tomcat application server installed on amazonlinux-java image |
The BaseImageBuilder.sh script is provided to build specifically these images.
You can build all images, including these images, by running the BuildImages.sh script.
Building the ActiveMQ Image
The following table shows the container image generated by ActiveMQ build options.
| Image Name | Description |
|---|---|
| activemq | The Apache ActiveMQ Java Messaging application installed on amazonlinux-java image |
The ActiveMqImageBuilder.sh script is provided to build specifically this image.
You can build all images, including this image, by running the BuildImages.sh script.
Building the MySQL Image
The MySQL build options will build the container image shown in the table below.
| Image Name | Description |
|---|---|
| mysql | A containerized MySQL database implementation, suitable for Commerce development or test environments |
The EpDbImageBuilder.sh script is provided to build specifically this image.
You can build all images, including this image, by running the BuildImages.sh script.
Building the Commerce Application Images
note
Prerequisites:
- A deployment package must be built and available.
- The base images must built and available.
The following table shows the container images generated by Commerce image build options.
| 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. |
The EpImageBuilder.sh script is provided to build specifically these images.
You can build all images, including these images, by running the BuildImages.sh script.
Building the Commerce Data-Pop Tool Image
note
Prerequisites:
- A deployment package must be built and available.
- The base images must built and available.
The Commerce Data Pop Dockerfile will build the container images shown in the table below.
| Image Name | Description |
|---|---|
| data-pop-tool | The Commerce Data Population tool and Java SDK installed on the amazonlinux image. |
For more information, see Containerized Elastic Path Data Population Tool.