Installation prerequisites

Before you install Sterling Order Management Software on OpenShift Container platform, review the planning steps and ensure to meet the required prerequisites.

  • What's new

    Read What's new for the new features and other information that is specific to the current release of Sterling Order Management Software.

  • Readme

    For a set of useful information, see the Readme document.

  • System requirements

    Generate the system requirements report and complete all the requirements that are listed.

  • Red Hat OpenShift Container platform and Kubernetes versions
    Sterling Order Management Software container is deployed on Red Hat OpenShift Container platform.
    • For more information about the Red Hat OpenShift Container platform supported version, see system requirements.
    • For more information about the Red Hat OpenShift Container platform Life-Cycle Policy, see Red Hat Customer Portal.
    • For more information about the Kubernetes version and version skew support policy, see Kubernetes Documentation.
    Important: Sterling Order Management Software containers run only on the supported Red Hat OpenShift Container platform and Kubernetes versions.

  • CPU architecture

    Ensure that you have a cluster with x86-64 bit CPU architecture or Power Systems 64-bit LE (Little Endian).

  • Install and configure Helm

    The Helm and Tiller supported version is 2.12.3. If you are using Helm version 3, Tiller is not needed.

  • Db2 configuration

    Ensure that the D2 database is installed and configured. For more information, see Configuring Db2.

    For development purposes, you can use IBM Db2 Docker images from Docker Hub. For more information, see IBM Db2 on Docker Hub.

    Note: You must install Db2 in UTC time zone.
  • IBM WebSphere MQ configuration

    Ensure that IBM MQ is installed and configured.

    You can install IBM MQ by using the e-assembly provided with Sterling Order Management Software. For more information, see Installing WebSphere MQ.

    For IBM MQ configuration, see Configuring IBM WebSphere MQ.

    For development purposes, you can use IBM MQ Docker images from Docker Hub. For more information, see IBM MQ on Docker Hub.

    Note: The Sterling Order Management Software application server container runs with the default username and the agent container runs with the omsuser username. Therefore, the users must be granted with the necessary privileges in IBM MQ to ensure that Sterling Order Management Software can work with JMS resources.
  • Install latest fix pack

    The Sterling Order Management Software certified containers are released every quarter with the latest fix pack available. When installing or upgrading the Helm chart, to load the fix pack factory setup, ensure to set the datasetup.fixPack.loadFPFactoryData parameter to true in values.yaml.

    In case you encounter any critical issue and expect the fix to be released in a fix pack earlier than the subsequent quarterly release, you must install the fix pack into the om-base container and generate the images for deployment.

    For more information about installing fix packs for Sterling Order Management Software containers, see Installing fix packs.

  • Authentication mechanism for integrations

    Sterling Order Management Software supports various ways of authentication mechanism for integrations. However, for container-based deployments it is recommended to use BASIC or STANDARD authentication. Therefore, ensure that you have read the security considerations. For more information about the security considerations, see Authentication mechanism for integrations.