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.

Container Layout

The Self-Managed Commerce container layout 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.json file that defines required external dependencies, such as Java version, Maven version, ActiveMQ version, and Tomcat version.
• Container entrypoint scripts
• Application configuration files
• Dockerfiles for building container images.

In the container layout, the artifacts are arranged and ready for building the Self-Managed Commerce application container images.

tip

For information about building the container layout, see Build Tools 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.

tip

For information about building the base images, see Build Tools Overview.

tip

For information about running the activemq and the optional mysql containers, see Containerized Environments.

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 build these images using tools provided by Elastic Path. Each container image is created by adding Java binaries and other files from the container layout to one of the base images.

tip

For information about building the container images, see Build Tools Overview.

tip

For information about running the containers, see Containerized Environments.

Deployment Package

The container layout artifact replaces and supersedes the deployment package in newer Self-Managed Commerce releases. The 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.json file that defines required external dependencies, such as Java version, Maven version, ActiveMQ version, and Tomcat version.

The previous generation of Self-Managed Commerce image build tools, called Elastic Path Docker, use the deployment package to create application container images.

Visualization

The following diagram describes the relationship between the artifacts.