Self-Managed Commerce Deployment Artifacts
The Self-Managed Commerce build and continuous integration (CI) processes generate several deployable artifacts. This topic describes the artifacts and their relationship.
Self-Managed Commerce Container Images
The Self-Managed Commerce container images are the images that run the Self-Managed Commerce application services and tools. You can build these images using tools provided by Elastic Path. Each container image is created by adding Java binaries and other files from the deployment package to one of the base images. For more information, see Containers Overview.
Base Images
The base images are container images that are used either as the foundation for the Self-Managed Commerce container images, or images that can be used to run non-Self-Managed Commerce services such as ActiveMQ and MySQL. These images do not contain or run Self-Managed Commerce application code. You build these images using tools provided by Elastic Path. For more information, see Containers Overview.
Deployment Package
The Self-Managed Commerce deployment package is an artifact that you build from the Self-Managed Commerce ep-commerce application source code. It is created by a Maven build process and is a Zip file that contains the following:
- The Java Web Archive (WAR) and configuration files for each of the Self-Managed Commerce applications.
- The Java binaries of various Self-Managed Commerce tools.
- The Liquibase files used to create and populate a Self-Managed Commerce database.
- The
ops-spec.jsonfile that defines required external dependencies, such as Java version, Maven version, ActiveMQ version, and Tomcat version.
The deployment package is required to build the Self-Managed Commerce application container images. For information on building the deployment package, see Build Deployment Package.
Visualization
The following diagram describes the relationship between the artifacts.
