Procedure (only v6.1.0)

You must use InstallService to install myFileGateway 2.0.

About this task

Follow these steps:

Procedure

  1. Install b2biAPIs.jar using the InstallService.cmd or InstallService.sh command.

    For more information, see Installing B2B REST APIs.

  2. Restart Sterling B2B Integrator.

Results

myFileGateway 2.0 is installed successfully.

Updating property values (only v6.1.0)

About this task

You can update the property values with new values even after installing myFileGateway 2.0.

Follow these steps:

Procedure

  1. Update the hostname or port details with new values in the sandbox.cfg file.
  2. Run the following commands to update the app-prod-env-config.js file with new values. 
    
Linux/Unix platform

./deployer.sh -t "build-noapp-wars"
./hardstop.sh
./run.sh
./deployer.sh -t "munge"

    
Windows platform

deployer.cmd -t "build-noapp-wars"
stopWindowsService.cmd
startWindowsService.cmd
deployer.cmd -t "munge"

Results

myFileGateway 2.0 is installed successfully with the new values.

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.

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.
  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.