Upgrading myFileGateway 2.0 (only v6.1.0)

You can upgrade to the latest version of myFileGateway 2.0 in single-node (non-clustered) and multiple-node (clustered) environments.

Upgrading in a single-node (non-clustered) environment (only v6.1.0)

In a non-clustered environment, when you want to upgrade with HTTPS option enabled (Use HTTPS Protocol? check box selected) using IIM or Response file, follow these steps:
  1. Enable REST HTTP Server Adapter in the dashboard and select Use SSL to Must.
  2. Install b2biAPIs.jar.
  3. Restart Sterling B2B Integrator.
Important: The above changes are not applicable from v6.1.0.1 and later versions.

Upgrading in a multiple-node (clustered) environment (only v6.1.0)

In a clustered environment, when you want to upgrade myFileGateway 2.0, you must update the REST HTTP Server Adapter hostname and port number for Node 2 (or above) with the REST HTTP Server Adapter hostname and port number from Node1 in the IIM panel or Response file.

Follow these steps as a workaround:

  1. Go to Node1 dashboard and create a copy of the REST HTTP Server Adapter.
  2. Edit the following fields in the copy of REST HTTP Server Adapter:
    1. Change the Environment from Node1 to Node2.
    2. Change the restapi.war file location with the respective path of Node 2.
  3. Restart Sterling B2B Integrator on Node 1 and Node 2.
Important: The above changes are not applicable from v6.1.0.1 and later versions.

Default deployment changes (v6.1.0.1 and later versions)

The system does not support hosting gateway.war on Liberty Server for IIM-based installations. By default, gateway.war is hosted on NoApp Server instead of Liberty Server.

Important: You cannot log in to myFileGateway 2.0 when you upgrade from v6.1.0.0 base version to v6.1.0.1 or from v6.1.0.0 base version to v6.1.0.2.

You encounter this problem only during upgrade to v6.1.0.1 or v6.1.0.2 from the 6.1.0.0 base version and will be fixed in v6.1.0.3.

To workaround this issue, follow these steps after installing the API jars:
  1. Modify these properties with values as CHANGEME in the sandbox.cfg file.
    
ASI_SERVICE_HOST = CHANGEME
ASI_SERVICE_PORT = CHANGEME
  2. Run setupfiles.sh or setupfiles.cmd, as required.
  3. Check if the gateway_application.yml file has the correct IP address and port number for the /myfilegateway URL.
  4. Restart the Sterling B2B Integrator server.

Hosting myFileGateway 2.0 on HTTP Server Adapter (v6.1.0.1 and later versions)

Follow these steps:
  1. Host myfg.war with URI as /myfg, gateway.war with URI as /gateway, and myfilegateway.war with URI as /myfilegateway on the same HTTP/HTTPs Server Adapter.
    Note: You must get all the .war files from the <install-dir>/noapp/deploy location.
    Note: If you select the key length 512, you must also use JDK 7 SR5. JDK 7 SR7 FP1 and above do not support key lengths below 1024.
  2. Update the ASI_SERVICE_HOST, ASI_SERVICE_PORT and MYFG_PROTOCOL in the sandbox.cfg file with details that match the HTTP/HTTPs Server adapter created in the above step.
  3. Run setupfiles.sh on Unix/Linux and setupfiles.cmd on Windows.
  4. Restart Sterling B2B Integrator.
Follow these additional steps if Perimeter Server is enabled on HTTP Server Adapter where myfg.war is hosted.
  1. Update the hostname or IP address of the Perimeter Server in the gateway_application.yml file.
    
myfilegateway:
path: /myfilegateway/**
url: http://<PS_HOST>:<http_port>/myfilegateway/
  2. Do not run the setupfiles.sh command.
  3. Restart Sterling B2B Integrator.

Integrating myFileGateway 2.0 with Sterling Secure Proxy and Sterling External Authentication Server (v6.1.0.1 and later versions)

To integrate myFileGateway 2.0 with Sterling Secure Proxy and Sterling External Authentication Server, you must follow the same steps used for integrating legacy myFileGateway.
Note: You can integrate with Sterling Secure Proxy and Sterling External Authentication Server only on v6.0.1.1 iFix2 and later versions.

REST HTTP Server Adapter changes (v6.1.0.1 and later versions)

From v6.1.0.1 and later versions, by default, the target Environment is set to All ASI Nodes for REST HTTP Server Adapter. This means the system deploys REST HTTP Server Adapters on all nodes, at once.

Before you perform an upgrade, you must manually remove all REST HTTP Server Adapters created during earlier releases. If not, you must remove them after upgrade and enable the newly added REST HTTP Server Adapters with the target Environment set to All ASI Nodes.