Preparing for OrderHub deployment

Configure Order Hub on the same server as an application server that has an smcfs context root.

For example, if smcfs is configured to https://smcfs-oms.public-domain.mycluster.com/smcfs then Order Hub must be set up as https://smcfs-oms.public-domain.mycluster.com/order-management.

Identifying the backend server

You can use the following options to specify the smcfs application server.

OMEnvironment specification for integrated deployment
  1. bindingAppServerName - Must refer to an application server name that contains the smcfs context root.

    For example, bindingAppServerName - smcfs.

    The following route gets created:

    Route location 
    https://<bindingAppServerName>-<namespace>.<host>/order-management
    For example, https://smcfs-oms.public-domain.mycluster.com/order-management
    ....
  image:    
  orderHub:
      base:
        imageName: om-orderhub-base
        tag: 10.0.2306.0-amd64
      extn:
        imageName: om-orderhub-ext
        tag: 10.0.2306.0-amd64
....
  servers:
  - appServer:
      ingress:
        contextRoots:
        - smcfs
    name: smcfs
....
  orderHub:
    bindingAppServerName: smcfs
    base:
      replicaCount: 1
    extn:
      replicaCount: 1
....
  2. If the route that is generated by using bindingAppServerName is not correct (for example, when you use a custom domain), then include customDomains with the applicable domains for the smcfs servers instead of bindingAppServerName.
    Note:
    • Order Hub cannot have its own custom domain. It must use the same custom domain that is defined for an appServer with the smcfs context root.
    • Order Hub cannot support both SSL enabled and SSL disabled in the same container. Therefore, if multiple custom domains are provided, the SSL setting must be the same in each domain.
    ....
  orderHub:
    adminURL: 'myDomain1.public-domain.mycluster.com'
....
Order Hub specification for independent deployment

adminURL - Must refer to an application server name that contains the smcfs context root.

For example, adminURL - smcfs.
apiVersion: apps.oms.ibm.com/v1beta1
kind: OrderHub
metadata:
  name: oms-orderhub
  namespace: oms
spec:
  adminURL: 'smcfs-oms.public-domain.mycluster.com'
....

Login URL for Order Hub

https://<bindingAppServerName>-<namespace>.<host>/order-management
or 
https://<custom-domain-host>/order-management
Note: More routes are created but are not accessed directly.

Environment variables (envVars)

The environment variables that can be included in the base or extn containers.

Integrated with Sterling™ Order Management System Software:
....
  orderHub:
    base:
      replicaCount: 1
      envVars: ohproperties
    extn:
      replicaCount: 1
      envVars: ohproperties

  serverProperties:
    envVars: 
    - groupName: ohproperties
      propertyList:
        ENABLE_PROPERTY_ONE: 'Y'
        ENABLE_PROPERTY_TWO: 'N'
....
Deployed independently: 
apiVersion: apps.oms.ibm.com/v1beta1
kind: OrderHub
metadata:
  name: oms-order-management
  namespace: oms
spec:
  orderHub:
    base:
      replicaCount: 1
      envVars: ohproperties
    extn:
      replicaCount: 1

  envVars:
  - groupName: ohproperties
    propertyList:
        ENABLE_PROPERTY_ONE: 'Y'
        ENABLE_PROPERTY_TWO: 'N'
...

JWT configuration

If you use a custom domain, or have an independent Order Hub deployment, add the following entry to OMEnvironment to ensure that JWT is setup on the appServer.
....
spec:
  common:
    jwt:
      issuer: 'oms'
....