Deploying myFileGateway 2.0 on AC nodes

You can deploy myfg.war file on AC nodes with a few changes before installing or upgrading Helm charts.

Perform these steps:
  1. Edit the values.yaml file.
    Open the respective ports in AC frontend service by updating below attribute.
    
ac.frontendService.extraPorts
ex:
    extraPorts:
      - name: myfg
        port: 30038
        targetPort: 30038
        nodePort: 30038
        protocol: TCP
    Note: The name of extraPort in myFileGateway 2.0 must be "myfg".
  2. Create extra paths in values.yaml for AC.
    
 extraPaths:
        - routePrefix: "myfg"
          path: "/myfg"
          servicePort: " myfg"
          enableHttps: <true or false based on SSL settings in Http Server Adapter>
    Note: The name of servicePort in myFileGateway 2.0 must be "myfg".
  3. Install or upgrade the Helm chart.
Note: If you set enableHttps to true, then you must patch the myFG and gateway routes with the certificate used during HTTP Server Adapter configuration. You must execute the below command to patch OCP route with the Sterling B2B Integrator certificate used while configuring TLS for HTTP Server Adapter.

DEST_CABUNDLE_FN=/<path to cert>/ASISslCert.cer 
DESTCABUNDLE=$(awk '{printf "%s\\n", $0}' ${DEST_CABUNDLE_FN})
oc patch route <name of route> -p '{"spec":{"tls":{"certificate":"'"${CERTIFICATE}"'", 
"key":"'"${KEY}"'" ,"caCertificate":"'"${CABUNDLE}"'", 
"destinationCACertificate":"'"${DESTCABUNDLE}"'"}}}'