This document provides an overview of available systems in the Intershop Commerce Platform.
Intershop Commerce Management
Intershop Order Management
Progressive Web App
Shared file system
User acceptance test environment
The Intershop Commerce Platform is a customizable SaaS/PaaS solution for complex B2B commerce scenarios. It consists of multiple loosely coupled apps and services combined in an API-oriented architecture.
Depending on the selected Intershop subscription and options, the platform is based on multiple single-tenant and multi-tenant applications, such as Intershop Commerce Management (ICM), Intershop Order Management (IOM), Intershop Progressive Web App (PWA), Intershop Customer Engagement Center (CEC), and/or BI Data Hub.
The Intershop Commerce Platform is typically tailored to the customer’s specific needs in a separate software customization project. The customization project is implemented by an Intershop implementation partner or Intershop Professional Services.
To ensure the highest quality of the customer’s commerce solution, Intershop also provides non-production environments and DevOps tooling to support professional continuous integration (CI) and continuous delivery (CD) processes.
The following table gives an overview of the different environments and clusters provided to the customer depending on the Intershop subscription:
The PRODUCTION (PRD) environment is used for end customers and by content editors.
The USER ACCEPTANCE TEST (UAT) environment is used for acceptance testing of new releases by the customer. It is typically initialized with anonymized production data to allow for realistic testing.
The INTEGRATION (INT) environment is used by the development teams for integration tests.
The following graphics show workflows and responsibilities for different processes and tools of our individual applications.
The next chapters give a more detailed overview of the CI/CD systems for the specific applications.
The left side shows the continuous integration environment. It is based on Azure DevOps and consists of a Git repository and build pipeline. The created software artifacts are stored in the binary repository. Releases can then be deployed to the VM-based non-production and production systems on the right side.
The new ICM version is based on containers and operated in a Kubernetes cluster. Custom container images are created during the build process based on Azure DevOps and stored in the container registry. The Helm-based deployment process is used to deploy container images to the non-production and production environments.
The PWA reference source code is cloned into the Azure DevOps Git repository and can be freely customized. As the result of the build process, the container image is pushed to the container registry. The Helm deployment process can be triggered and the container image is pulled from the container registry and deployed into the namespaces of the non-production and production Kubernetes clusters.
Custom IOM container images are created during the build process (left side) based on the IOM base images and pushed to the container registry. The Helm deployment process can be triggered and the container images are pulled from the container registry and deployed into the namespaces of the non-production and production Kubernetes clusters.
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.