Accessing myFileGateway 2.0 in a multiple-node (clustered) environment (only v6.1.0)

You can access myFileGateway 2.0 in a multiple-node environment where Sterling B2B Integrator and B2B APIs are installed on separate nodes.

The following properties are introduced in the myFileGateway 2.0 GUI. You must provide values to these properties before installation to access myFileGateway 2.0 successfully. These values are automatically updated in the sandbox.cfg file. These values are further used in the gateway_application.yaml file internally to automate the installation and configure myFileGateway 2.0.
  • API_Gateway_IP and API_Gateway_Port - Provides IP address and Port number information where Sterling B2B Integrator APIs are installed.
  • ASI Service Hostname or IP Address and ASI Service Port - Provides IP address and port number of Sterling B2B Integrator application.
  • REST HTTP Server Adapter Service hostname or IP Address and REST HTTP Server Adapter Service Port - Provides IP address and port number of the REST HTTP Server Adapter.
Important: The above changes are not applicable from v6.1.0.1 and later versions.

The following sections explain the procedure to include the above properties and enable myFileGateway 2.0 using different installation methods.

Using IIM (only v6.1.0)

  1. Install Sterling B2B Integrator.
  2. Enter values for API_Gateway_IP , API_Gateway_Port , ASI Service Hostname or IP Address , ASI Service Port, REST HTTP Server Adapter Service hostname or IP Address, and REST HTTP Server Adapter Service Port in the MyFG 2.0 Information (Optional) panel. These values are automatically updated in sandbox.cfg.
    Note:
    • If no values are added, these fields are empty (API_GATEWAY_IP and API_GATEWAY_PORT) and these fields have <CHANGEME>as hardcoded (ASI_SERVICE_HOST and ASI_SERVICE_PORT ) in sandbox.cfg.
    • For REST_HTTP_SERVER_ADAPTER_SERVICE_HOST and REST_HTTP_SERVER_ADAPTER_SERVICE_PORT, the default value is set to the value of the host address where myFileGateway 2.0 is installed and port of the REST HTTP Server Adapter respectively.
  3. Click Install.
  4. Install b2biAPIs.jar. This internally calls deployer.sh, which updates the app-prod-env-config.js file.
  5. Restart Sterling B2B Integrator and Liberty Server.
Important: The above changes are not applicable from v6.1.0.1 and later versions, since the MyFG 2.0 Information panel is not available.

Using Response file (only v6.1.0)

You must include the following rows in the Response file to include the above properties before installation.

<data key='user.sb.API_GATEWAY_IP,com.ibm.sterling.integrator.install.offering' value='<gateway_ip>'/>
<data key='user.sb.API_GATEWAY_PORT,com.ibm.sterling.integrator.install.offering' value='<gateway_port>'/>
<data key='user.sb.ASI_SERVICE_HOST,com.ibm.sterling.integrator.install.offering' value='<ASI_Install_IP>'/>
<data key='user.sb.ASI_SERVICE_PORT,com.ibm.sterling.integrator.install.offering' value='<ASI_Install_port>'/>
<data key='user.sb.user.sb.REST_HTTP_SERVER_ADAPTER_SERVICE_HOST,com.ibm.sterling.integrator.install.offering' value='<REST_HTTP_SERVER_Adapter_host>'/>
<data key='user.sb.user.sb.REST_HTTP_SERVER_ADAPTER_SERVICE_PORT,com.ibm.sterling.integrator.install.offering' value='<REST_HTTP_SERVER_Adapter_port>'/>
Important: The above changes are not applicable from v6.1.0.1 and later versions.

Using Docker container (only v6.1.0)

You must include these properties in the setup.cfg file.
  • API_GATEWAY_IP
  • API_GATEWAY_PORT
  • ASI_SERVICE_HOST
  • ASI_SERVICE_PORT
  • REST_HTTP_SERVER_ADAPTER_SERVICE_HOST
  • REST_HTTP_SERVER_ADAPTER_SERVICE_PORT

By default, the above properties are set to the hardcoded value <CHANGEME> in setup.cfg.

If you wish to modify or specify a different URL in a Docker instance, then you can enter it in setup.cfg and remove the existing b2bidockerinstalldone.txt file and restart the Docker container.

This calls deployer.sh internally, which updates sandbox.cfg with the given property key/value.

If sandbox.cfg contains all the above properties with values other than default, then that IP address and port is used in the gateway_application.yaml for further processing, else the default URL is used.

Important: The above changes are not applicable from v6.1.0.1 and later versions.