Preparing for Sterling Call Center deployment

Configure Sterling™ Call Center on the same domain as an application server that has an icc context root. You must identify the backend server and the login URL for Sterling Call Center.

For example, if icc is configured to https://icc-oms.public-domain.mycluster.com/icc then Sterling Call Center must be set up as https://icc-oms.public-domain.mycluster.com/call-center.

Identifying the backend server

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

OMEnvironment specification for integrated deployment

bindingAppServerName - Must refer to an application server name that contains the icc context root.

For example, bindingAppServerName - icc.

The following route gets created:

Route location

https://<bindingAppServerName>-<namespace>.<host>/call-center

For example, https://icc-oms.public-domain.mycluster.com/call-center.

....
  image:    callCenter:
      base:
        imageName: om-call-center-base
        tag: 10.0.2306.0-amd64
      extn:
        imageName: om-call-center-ext
        tag: 10.0.2306.0-amd64
....
  servers:
  - appServer:
      ingress:
        contextRoots:
        - icc
    name: icc
....
  callCenter:
    bindingAppServerName: icc
    base:
      replicaCount: 1
    extn:
      replicaCount: 1
....

If the route that is generated by using bindingAppServerName is not correct (for example, when using a custom domain), then include customDomains with the applicable domains for the icc servers instead of bindingAppServerName.
Note:
- Sterling Call Center cannot have its own custom domain. It must use the same custom domain that is defined for an appServer with the icc context root.
- Sterling Call Center 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.
```
....
  callCenter:
    customDomains:
    - host: myDomain1.public-domain.mycluster.com
      ssl:
        enabled: false
    - host: myDomain2.public-domain.mycluster.com
      ssl:
        enabled: false
....
  servers:
  - appServer:
      ingress:
        contextRoots:
        - smcfs
        - icc
        customDomains:
          - host: myDomain1.public-domain.mycluster.com
            ssl:
              enabled: false
          - host: myDomain2.public-domain.mycluster.com
            ssl:
              enabled: false
....
```

Sterling Call Center specification for independent deployment

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

For example,

adminURL -
icc

apiVersion: apps.oms.ibm.com/v1beta1
kind: CallCenter
metadata:
  name: oms-ccenter
  namespace: oms
spec:
  adminURL: 'icc-oms.public-domain.mycluster.com'
....

customDomains with the applicable domains for the icc servers.

apiVersion: apps.oms.ibm.com/v1beta1
kind: CallCenter
metadata:
  name: oms-ccenter
  namespace: oms
spec:
....
  networking:
    ingress:
      host: public-domain.mycluster.com
      customDomains:
      - host: appserver-oms.public-domain.mycluster.com
        ssl:
          enabled: true
      - host: appserver.public-domain.mycluster.com
        ssl:
          enabled: true
....

Login URL for Sterling Call Center

https://<bindingAppServerName>-<namespace>.<host>/call-center

https://<custom-domain-host>/call-center

Note: More routes are created but are not accessed directly.