Sample YAML for Control Center user interface

Sample YAML for configuring the instance of the Control Center user interface that is being created.

The following examples use ftm-demo as the namespace. Also, replace the OfferingVersionNumber text with the value of the operand for the version that you are deploying.

You can use the following table to find the deployment version information that you need to use with the sample YAML.
Table 1. Operator to install for the versions of FTM
IBM® product version of FTM The deployment information for this version
3.2.13
  • The channel is stable-v4.5
  • The operand is 3.2.13.0
  • The version of the operator is 4.5.0

Corporate Payment Services

This sample YAML is for Corporate Payment Services.
apiVersion: ftm.ibm.com/v1
kind: FTM
metadata:
  name: ftm-demo
spec:
  license:
    accept: true
  version: OfferingVersionNumber
  account:
    imagePullPolicy: IfNotPresent
  config:
    instance:
      solution:
        - cps-mp
    ui:
      domain: apps.ftm.example.com # <UI external route>
      ewsService: ews.example.com # <EWS external route>
      externalComponents:
        businessRulesEngine:
          host: businessRulesEngine.example.com
          port: 3000
        servicesEngine:
          host: 127.0.0.1
          port: 3000
        distributionEngine:
          host: distributionEngine.example.com
          port: 3000
        settlementEngine:
          host: settlementEngine.example.com
          port: 3000
        riskEngine:
          host: riskEngine.example.com
          port: 3000
        rtpEngine:
          host: rtpEngine.example.com
          port: 3000
        approvalsEngine:
          host: approvalsEngine.example.com
          port: 3000
        gatewayEngine:
          host: gatewayEngine.example.com
          port: 3000
        nocEngine:
          host: nocEngine.example.com
          port: 3000
        vettingEngine:
          host: vettingEngine.example.com
          port: 3000
        businessRulesServer:
          host: businessRulesServer.example.com
          port: 3000
        businessRulesManager:
          host: businessRulesManager.example.com
          port: 3000
    security:
      networkPolicy:
        egress:
          - ports: # DB2
              - protocol: TCP
                port: 50000
            to:
              - ipBlock:
                  cidr: 0.0.0.0/0 # <External Db2 CIDR block>
          - ports: # MQ
              - protocol: TCP
                port: 1414
            to:
              - ipBlock:
                  cidr: 0.0.0.0/0 # <External IBM MQ CIDR block>
          - ports: # WebSphere
              - protocol: TCP
                port: 58814
              - protocol: TCP
                port: 58448
            to:
              - ipBlock:
                  cidr: 0.0.0.0/0 # <WebSphere CIDR block>
          - ports: # OIDC
              - protocol: TCP
                port: 443
              - protocol: TCP
                port: 8443
        ingress:
          - ports:
              - protocol: TCP
                port: 3000
              - protocol: TCP
                port: 3001
              - protocol: TCP
                port: 9443
      certificate:
        secretName: ftm-ssl-cert-secret
      mtls:
        label: ftmserver
      oidc:
        oAuth2ClientID: EXAMPLE123ID # <OAuth 2 client ID>
        oAuth2Issuer: exampleIssuer # <OAuth 2 issuer>
        oAuth2DiscoveryEndpoint: https://example.com/oidc/endpoint/default # <OAuth 2 discovery endpoint>
        oAuth2ClientSecret:
          valueFrom:
            secretKeyRef:
              name: ftm-oidc-clientsecret
              key: clientsecret
    mq:
      enableConfigJob: false
      host: mq.example.com # <IBM MQ host>
      port: 1414
      enableTLS: true
      queueManagerName: FTM.QMANAGER
      certificate:
        secretName: ftm-mq-ssl-cert-secret
      channel: SYSTEM.DEF.SVRCONN
    database:
      database: FTMDB
      username: ftmuser
      port: 50000
      schema: FTM
      host: db2.example.com # <Db2 host>
      enableTLS: true
      certificate:
        valueFrom:
          secretKeyRef:
            key: ca.crt
            name: ftm-db2-ssl-cert-secret
      password:
        valueFrom:
          secretKeyRef:
            key: DB_PASSWORD
            name: ftm-application-secret
  storage:
    default:
      spec:
        storageClassName: "managed-nfs-storage"
        accessModes:
          - ReadWriteMany
        resources:
          requests:
            storage: 10Gi

Digital Payments

This sample YAML is for Digital Payments 
apiVersion: ftm.ibm.com/v1
kind: FTM
metadata:
  name: ftm-demo
spec:
  license:
    accept: true
  version: OfferingVersionNumber
  account:
    imagePullPolicy: IfNotPresent
  config:
    instance:
      solution:
        - dp-mp
    ui:
      domain: apps.ftm.example.com # <UI external route>
      ewsService: ews.example.com # <EWS external route>
      externalComponents:
        businessRulesEngine:
          host: businessRulesEngine.example.com
          port: 3000
        servicesEngine:
          host: 127.0.0.1
          port: 3000
        distributionEngine:
          host: distributionEngine.example.com
          port: 3000
        settlementEngine:
          host: settlementEngine.example.com
          port: 3000
        riskEngine:
          host: riskEngine.example.com
          port: 3000
        rtpEngine:
          host: rtpEngine.example.com
          port: 3000
        approvalsEngine:
          host: approvalsEngine.example.com
          port: 3000
        gatewayEngine:
          host: gatewayEngine.example.com
          port: 3000
        nocEngine:
          host: nocEngine.example.com
          port: 3000
        vettingEngine:
          host: vettingEngine.example.com
          port: 3000
        businessRulesServer:
          host: businessRulesServer.example.com
          port: 3000
        businessRulesManager:
          host: businessRulesManager.example.com
          port: 3000
    security:
      networkPolicy:
        egress:
          - ports: # Db2
              - protocol: TCP
                port: 50000
            to:
              - ipBlock:
                  cidr: 0.0.0.0/0 # <External Db2 CIDR Block>
          - ports: # MQ
              - protocol: TCP
                port: 1414
            to:
              - ipBlock:
                  cidr: 0.0.0.0/0 # <External IBM MQ CIDR block>
          - ports: # WebSphere
              - protocol: TCP
                port: 58814
              - protocol: TCP
                port: 58448
            to:
              - ipBlock:
                  cidr: 0.0.0.0/0 # <WebSphere CIDR block>
          - ports: # OIDC
              - protocol: TCP
                port: 443
              - protocol: TCP
                port: 8443
        ingress:
          - ports:
              - protocol: TCP
                port: 3000
              - protocol: TCP
                port: 3001
              - protocol: TCP
                port: 9443
      certificate:
        secretName: ftm-ssl-cert-secret
      mtls:
        label: ftmserver
      oidc:
        oAuth2ClientID: EXAMPLE123ID # <OAuth 2 client ID>
        oAuth2Issuer: exampleIssuer # <OAuth 2 issuer>
        oAuth2DiscoveryEndpoint: https://example.com/oidc/endpoint/default # <OAuth 2 discovery endpoint>
        oAuth2ClientSecret:
          valueFrom:
            secretKeyRef:
              name: ftm-oidc-clientsecret
              key: clientsecret
    mq:
      enableConfigJob: false
      host: mq.example.com # <IBM MQ host>
      port: 1414
      enableTLS: true
      queueManagerName: FTM.QMANAGER
      certificate:
        secretName: ftm-mq-ssl-cert-secret
      channel: SYSTEM.DEF.SVRCONN
    database:
      database: FTMDB
      username: ftmuser
      port: 50000
      schema: FTM
      host: db2.example.com # <Db2 host>
      enableTLS: true
      certificate:
        valueFrom:
          secretKeyRef:
            key: ca.crt
            name: ftm-db2-ssl-cert-secret
      password:
        valueFrom:
          secretKeyRef:
            key: DB_PASSWORD
            name: ftm-application-secret
  storage:
    default:
      spec:
        storageClassName: "managed-nfs-storage"
        accessModes:
          - ReadWriteMany
        resources:
          requests:
            storage: 10Gi

High Value Payments

This sample YAML is for High Value Payments.
apiVersion: ftm.ibm.com/v1
kind: FTM
metadata:
  name: ftm-demo
spec:
  license:
    accept: true
  version: OfferingVersionNumber
  account:
    imagePullPolicy: IfNotPresent
  config:
    instance:
      solution:
        - hvp-mp
    ui:
      domain: apps.ftm.example.com # <UI external route>
      ewsService: ews.example.com # <EWS external route>
      externalComponents:
        businessRulesEngine:
          host: businessRulesEngine.example.com
          port: 3000
        servicesEngine:
          host: 127.0.0.1
          port: 3000
        distributionEngine:
          host: distributionEngine.example.com
          port: 3000
        settlementEngine:
          host: settlementEngine.example.com
          port: 3000
        riskEngine:
          host: riskEngine.example.com
          port: 3000
        rtpEngine:
          host: rtpEngine.example.com
          port: 3000
        approvalsEngine:
          host: approvalsEngine.example.com
          port: 3000
        gatewayEngine:
          host: gatewayEngine.example.com
          port: 3000
        nocEngine:
          host: nocEngine.example.com
          port: 3000
        vettingEngine:
          host: vettingEngine.example.com
          port: 3000
        businessRulesServer:
          host: businessRulesServer.example.com
          port: 3000
        businessRulesManager:
          host: businessRulesManager.example.com
          port: 3000
    security:
      networkPolicy:
        egress:
          - ports: # DB2
              - protocol: TCP
                port: 50000
            to:
              - ipBlock:
                  cidr: 0.0.0.0/0 # <External Db2 CIDR block>
          - ports: # MQ
              - protocol: TCP
                port: 1414
            to:
              - ipBlock:
                  cidr: 0.0.0.0/0 # <External IBM MQ CIDR block>
          - ports: # WebSphere
              - protocol: TCP
                port: 58814
              - protocol: TCP
                port: 58448
            to:
              - ipBlock:
                  cidr: 0.0.0.0/0 # <WebSphere CIDR block>
          - ports: # OIDC
              - protocol: TCP
                port: 443
              - protocol: TCP
                port: 8443
        ingress:
          - ports:
              - protocol: TCP
                port: 3000
              - protocol: TCP
                port: 3001
              - protocol: TCP
                port: 9443
      certificate:
        secretName: ftm-ssl-cert-secret
      mtls:
        label: ftmserver
      oidc:
        oAuth2ClientID: EXAMPLE123ID # <OAuth 2 client ID>
        oAuth2Issuer: exampleIssuer # <OAuth 2 issuer>
        oAuth2DiscoveryEndpoint: https://example.com/oidc/endpoint/default # <OAuth 2 discovery endpoint>
        oAuth2ClientSecret:
          valueFrom:
            secretKeyRef:
              name: ftm-oidc-clientsecret
              key: clientsecret
    mq:
      enableConfigJob: false
      host: mq.example.com # <IBM MQ host>
      port: 1414
      enableTLS: true
      queueManagerName: FTM.QMANAGER
      certificate:
        secretName: ftm-mq-ssl-cert-secret
      channel: SYSTEM.DEF.SVRCONN
    database:
      database: FTMDB
      username: ftmuser
      port: 50000
      schema: FTM
      host: db2.example.com # <Db2 host>
      enableTLS: true
      certificate:
        valueFrom:
          secretKeyRef:
            key: ca.crt
            name: ftm-db2-ssl-cert-secret
      password:
        valueFrom:
          secretKeyRef:
            key: DB_PASSWORD
            name: ftm-application-secret
  storage:
    default:
      spec:
        storageClassName: "managed-nfs-storage"
        accessModes:
          - ReadWriteMany
        resources:
          requests:
            storage: 10Gi