Meeting the system requirements

Review the minimum and recommended system requirements, container runtime clusters, database, and message queue server considerations.

Note:
  • The connection between the client and the ingress must be always on https instead of http.
  • Supported architecture is Intel/AMD only. Effective September 2021, support for Power architecture is withdrawn.

Procedure

  1. Ensure that you review the following resource requirements:
    Minimum requirements
    The Operator by default uses the following resources:
    • 2560Mi memory for application server.
    • 1024Mi memory for each agent or integration server and health monitor.
    • 1 CPU core for application server.
    • 0.5 CPU core for each agent or integration server and health monitor.
    Recommended requirements
    To achieve an approximate throughput of:
    • 350 thousand order lines per hour with corresponding inventory calls
    • 3 million inventory item updates or lookups per hour
    • 200 call center users
    • 1000 store users

    Use the following resources:

    • Master node (3 nodes each with):
      • 4 CPU cores
      • 16 GB memory
    • Worker nodes (3 worker nodes each with):
      • 16 CPU cores each
      • 64 GB memory each

    To customize requirements according to your workload, contact your Customer Success Manager to get IBM Techline engaged.

  2. Ensure that you have access to a supported Red Hat Openshift cluster. For more information, see Software Product Compatibility Reports.
  3. Install any one of the supported databases: DB2, Oracle, or PostgreSQL. For more information about the database versions, see Software Product Compatibility Reports. Ensure that the database is accessible from within the cluster. Ensure that the database, application server, and agent server are all in the same time zone. Also, ensure that the time zone is compatible with locale code as specified in the application. The containers are by default deployed in UTC time zone and the locale code is set to en_US_UTC. Therefore, ensure that you deploy the database in UTC time zone.
  4. Ensure that you set the installation locale code to en_US_UTC timezone to match with the other timezones and avoid any timezone calculation errors. The installation locale code is by default set to en_US_EST.
  5. If you are using Oracle or PostgreSQL database or for any other customizations, ensure to customize and regenerate custom images as needed. For more information, see Customizing and generating container images.
  6. Install IBM MQ or any other JMS server. For more information about the system requirements, see Software Product Compatibility Reports. Ensure that the IBM MQ server is accessible from within the cluster.
  7. If you are using the integrated Developer Toolkit, before you create custom extensions for the Sterling Order Management System Software, set up your Developer Toolkit environment for creating and testing extensions for your service applications. For more information, see Setting up the Integrated Developer Toolkit environment.
  8. If you plan to upgrade to a containerized model from a non-container model or any version prior 10.0, see Upgrading to Sterling Order Management System Software containers.