Deployment prerequisites

Before you start deploying IBM Sterling Order Management SoftwareIBM Field Sales on OpenShift Container platform for Db2 or Oracle database, complete the required prerequisites.
Important: To complete the prerequisites, you must have Administrator privileges.
  • Review and complete the installation prerequisites.
  • Configure the cluster to automatically pull the required images from IBM Entitled Registry and load them to OpenShift Container platform.
  • Download and configure the command line utilities.
  • Read the Readme file.
  • If you are deploying Sterling Order Management Software to a non-default namespace, ensure to define RBAC.
    The following sample code illustrates RBAC for the default service account for the target namespace as <namespace>.
    kind: Role
    apiVersion: rbac.authorization.k8s.io/v1
    metadata:
      name: oms-role-<namespace>
      namespace: <namespace>
    rules:
    - apiGroups: [""]
      resources: ["secrets"]
      verbs: ["get", "watch", "list","create","delete","patch","update"]
    
    -------
    
    kind: RoleBinding
    apiVersion: rbac.authorization.k8s.io/v1
    metadata:
      name: oms-rolebinding-<namespace>
      namespace: <namespace>
    subjects:
    - kind: ServiceAccount
      name: default
      namespace: <namespace>
    roleRef:
      kind: Role
      name: oms-role-<namespace>
      apiGroup: rbac.authorization.k8s.io
  • Create a PersistentVolume.

    - In OpenShift Container platform, create a PersistentVolume with Access mode as ReadWriteMany and Storage greater or equal to 10Gi.

    Ensure that the PersistentVolume storage is accessible by all containers across the cluster.

    For more information, see Configuring persistent volumes in OpenShift Container platform.

    Note: Ensure that the owner group of the PersistenceVolume directory has write access, and the owner group ID is specified in the global.persistence.securityContext.fsGroup parameter of the Sterling Order Management Software Helm chart.
  • Create a secret by using the datasource connectivity details.
    Note: It is recommended that you prefix the release name to the secret name.
    To create a secret, complete the following steps:
    1. Create a yaml file. For example, oms_secret.yaml as follows and set the appropriate values for all the parameters.
      apiVersion: v1
      kind: Secret
      metadata:
        name: "<Release-name>-oms-secret"
      type: Opaque
      stringData:
        consoleadminpassword: "<liberty console admin password>"
        consolenonadminpassword: "<liberty console non admin password>"
        dbpassword: "<database user password>"
        
    2. Run the following command to encode the values in your yaml file and create a secret.
      oc create -f oms_secret.yaml -n <namespace>
  • If you have not enabled anyuid Security Context Constraint (SCC), enable it to the service account that is used for the deployment of Sterling Order Management Software on OpenShift Container platform by using the following command:
    oc adm policy add-scc-to-user anyuid -z <service_account_name>
  • If you have not enabled the edit permission to the service account, enable it for the specific project by using the following command:
    oc policy add-role-to-user edit system:serviceaccount:<project_name>:<service_account_name>