Deprecated

Using the downloaded Helm chart

You can deploy the application server and agents by using the Helm chart that you have downloaded.

Deploying the Application server

To deploy the Application Server and Agents by using the downloaded Helm chart, complete the following steps:

  1. Review and complete the deployment prerequisites.
  2. Download and extract the Sterling Order Management System Software Helm chart to a temporary folder, henceforth referred as Chart Directory.
  3. Browse to the Chart Directory and edit the values of values.yaml file.
    • Accept the license of Sterling Order Management System Software application by setting the value of global.license property to “accept”.
    • Set the value of appserver.service.https.port property to 9080 to enable the communication of ingress with the Liberty Application server.
    • Set the value of appserver.ingress.host to a unique sub-domain of the cluster’s host name through which the deployed application is exposed.

      For the list of supported values, see the Readme file.

  4. Run the following command to install the Sterling Order Management System Software application in OpenShift Container Platform by using the updated Sterling Order Management System Software Helm chart:
    helm install <release_name> -f values.yaml ./<ibm-oms-edition> --timeout 3600s --namespace <namespace>
After successfully deploying the Application Server, complete any of the following tasks:
  • If you are using Kubernetes cluster, access the following application URLs:
    • <https or http>://<appserver.ingress.host>/smcfs
    • <https or http>://<appserver.ingress.host>/sbc
    • <https or http>://<appserver.ingress.host>/sma
    • <https or http>://<appserver.ingress.host>/isccs
    • <https or http>://<appserver.ingress.host>/wsc
    • <https or http>://<appserver.ingress.host>/isf
    • <https or http>://<appserver.ingress.host>/adminCenter
    Note: For routes, when you directly click any of the following application URLs, the login page is not displayed.
    • https://<cluster-url>/smcfs
    • https://<cluster-url>/sbc
    • https://<cluster-url>/sma
    • https://<cluster-url>/isccs
    • https://<cluster-url>/wsc
    • https://<cluster-url>/isf
    Therefore, to directly access the login page provide the complete URL as follows:
    • https://<cluster-url>/smcfs/console/login.jsp
    • https://<cluster-url>/sbc/sbc/login.do
    • https://<cluster-url>/sma/sma/login.do
    • https://<cluster-url>/isccs/isccs/login.do
    • https://<cluster-url>/wsc/store/login.do
    • https://<cluster-url>/isf/store/login.do
  • If you are using OpenShift Container Platform cluster, for multiple application images, routes are created by using certain conditions based on the provided values. For more information about deploying multiple application images, see the Readme file.
Troubleshooting:

Problem: When you deploy the Sterling Order Management System Software Helm chart on OpenShift Container Platform for the first time against a fresh database, the application server pod fails to start.

Solution: Redeploy the Sterling Order Management System Software Helm chart on OpenShift Container Platform.

Deploying the Agents

Note: You cannot use the Terminate Server on Idle field when deploying containers on Kubernetes through Sterling Order Management System Software Helm chart.

Before you begin, ensure that the following prerequisites are completed:
  • Deployed the Application server.
  • Configured agents in the Applications Manager.
  • Configured IBM MQ with JMS resources and generate an IBM MQ binding file. For more information about IBM MQ binding files, see Creating JMS bindings in IBM WebSphere MQ.
  • Created the ConfigMap by running the following command:
    oc create configmap <config map name> --from-file=<path_to_.bindings_file> -n <namespace>
    Here,
    • <config map name> - refers to the name of ConfigMap.
    • <path_to_.bindings_file> - refers to the path of the *.bindings file.
    • <namespace> - refers to the namespace where the Sterling Order Management System Software Docker images are loaded.
Deploy agents by completing the following steps:
  1. Review and complete the deployment prerequisites.
  2. Download the Helm chart to a temporary folder, henceforth referred as Chart Directory.
  3. Browse to the Chart Directory and edit the values of values.yaml file.

    Ensure to accept the license of Sterling Order Management System Software application by setting the value of global.license property to “accept”.

    For the list of supported values, see the Readme file.

    Configure the agent server details in the values.yaml by using the following code snippet:
    - group: "Logical Group 1"
  name: ["<agent server 1>", "<agent server 2>"]

    Here, <agent server 1> and <agent server 2> refers to the agent server names that are configured in the Applications Manager. You can define one or more agent server names.

  4. Run the following command to install the Sterling Order Management System Software agent servers in OpenShift Container Platform by using the updated Sterling Order Management System Software Helm chart:
    helm install <release_name> -f values.yaml ./<ibm-oms-edition> --timeout 3600s --namespace <namespace>