Deployment architecture

The Sterling Order Management System Software composes of three basic image types, which are om-app, om-agent, and om-base.

The om-base image is used to create a customization runtime that can be used to apply and integrate customizations and also to build new custom images of om-app and om-agent. Further, the om-app images can also be built for specific applications.

The different om-app images that are built by using the customization runtime can be deployed with a dedicated route or ingress to expose the applications in om-app images. Routes are created only if you are using a Red Hat® OpenShift® Container Platform cluster. For any other Kubernetes cluster, ingress is created.

The om-agent image can be used to create deployments that run different agents or integration servers that are configured in the system.

Ensure that the application and agent containers are colocated in the same Kubernetes cluster as multi-cluster deployment of these containers is not supported. This might cause issues with certain health monitoring APIs and cache propagation.

The following diagram illustrates the basic environment configuration after deployment of the default Sterling Order Management System Software images:
Figure 1. Architecture of Sterling Order Management System deployment on Red Hat OpenShift Container Platform
Sterling Order Management System deployment on Red Hat Open Shift Container Platform
Note: The base image (om-base) is not a deployable container and is available to create customizations for your applications and agent features that are outside of the deployment cluster. For more information, see Customizing and generating container images.