Containerized Environments
Each Self-Managed Commerce environment is composed of separate components that provide different functionality and work together as described in Self-Managed Commerce Deployment Solutions and Self-Managed Commerce Application Servers Guideline. The core application services and ActiveMQ component typically run as containers. The relational database typically runs as a container in development and test environments.
Containerized Components
This section summarizes the container images created by the containerization tools.
Self-Managed Commerce Application Services
The table below summarizes the Self-Managed Commerce applications that are components of a Commerce environment.
| Application | Purpose | Container Image |
|---|---|---|
| Cortex | The primary Commerce API service. The container image contains both the main Cortex web-application and the Cortex Studio web-application. For more information, see Introduction to Cortex. | cortex |
| Commerce Manager | Internal business user tooling. For more information, see Commerce Manager Overview. | cm |
| Search Primary | Indexes Commerce data using Apache Solr and is the search-index source of truth. The search primary is configured as the Apache Solr master. For more information about the Search Server application, see Search Server in Self-Managed Commerce. | search |
| Search Secondary | Exposes search index data to API clients. The search secondary servers are configured as the Apache Solr slaves. For more information about the Search Server, see Search Server in Self-Managed Commerce. | search |
| Batch Server | Runs scheduled jobs. For more information, see Batch Server Quartz Jobs. | batch |
| Integration Server | Runs integration code. For more information, see Integration Server Overview. | integration |
| Data Sync WebApp | Synchronizes data changes from an authoring environment to the corresponding live environment. For more information about the application, see Data Sync WebApp Overview. | data-sync |
| Wiremock | Simulate external system responses to assist with the development of integration features. This service is only deployed on test environments when actual integrations are not implemented. | mock |
Self-Managed Commerce Data Population
The Self-Managed Commerce Data Population tool is used to either initialize a new Commerce database or to update an existing Commerce database. For more information about the application, see Data Population Overview.
| Application | Purpose | Container Image |
|---|---|---|
| Data population Tool | A Java process that is run to create a new Commerce database or update an existing database. It is typically run as a job; it is launched and then runs to completion. | data-pop-tool |
Third-Party Containerized Services
The table below summarizes third-party containerized services that are also components of a Commerce environment.
| Application | Purpose | Container Image |
|---|---|---|
| ActiveMQ | Java Messaging Service for Commerce integrations. | activemq |
| MySQL | Containerized MySQL database implementation suitable for development and test environments. | mysql |