Deploying myFileGateway 2.0 on HTTP Server Adapter using Certified Container

To run myFileGateway2.0 inside your secure network, no configuration is required. An HTTP Server adapter configuration (named HTTP Server Adapter) comes with Sterling File Gateway that enables the clients on the same network as Sterling File Gateway to access myFileGateway 2.0.

Patching OCP route with Sterling B2B Integrator certificate

You must execute the below command to patch OCP route with the Sterling B2B Integrator certificate used while configuring TLS for HTTP Server Adapter.

Here is the command to patch OCP route:

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}"'", 

To deploy myFileGateway 2.0 on HTTP Server Adapter, you must perform certain necessary changes before installing or upgrading Helm charts.

Note: (v6.1.0.1)

You must deploy gateway.war and myfilegateway.war on the same HTTP Server Adapter where myFileGateway 2.0 is deployed.