
Please find the descriptions for Apache products which can be suitable for B2B Integrations. #from the local gateway to the local queue manager. #the connection from the remote fasp gateway to the local fasp gateway

#from the local fasp gateway to the remote fasp gateway #connection from the local queue manager to the local fasp gateway Similarly the remote FASP gateway is 192.168.1.108. Here local queue manager and FASP are on the same machine - 192.168.1.107. In case if Queue manager and FASP gateway are on the same server. Start the remote gateway by running the following command on the remote gateway machine: Start the local gateway by running the following command on the local gateway machine: Edit it to set the remote gateway definitions:Īt each end of the connection, change the channel definition to connect to the port that the local gateway is listening on.Ĭhange the queue manager channel on the local queue manager to connect to the local Aspera gateway using conname 9.20.193.107(1500).Ĭhange the queue manager channel on the remote queue manager to connect to the remote Aspera gateway using conname 9.20.192.115(1500). Modify the gateway.toml file in the /etc/fasp.io directory that was created by the install. Repeat the previous step to define an Aspera gateway connection on the remote gateway machine. Modify the gateway.toml file in the /etc/fasp.io directory that was created by the install.Įdit it to set the local gateway definitions. The queue manager channel on the remote queue manager is changed to connect to the remote Aspera gateway using conname 9.20.192.115(1500).ĭefine an Aspera gateway connection on the local gateway machine: The queue manager channel on the local queue manager is changed to connect to the local Aspera gateway using conname 9.20.193.107(1500). Both queue managers are listening on port 1414.

The remote queue manager is running on a machine with IP address 9.20.121.25.

The local queue manager is running on a machine with IP address 9.20.121.5. The IP address of the remote gateway machine is 9.20.192.115. The IP address of the local gateway machine is 9.20.193.107. This example defines an Aspera gateway connection on two machines running Linux. SystemD startup file: /etc/systemd/system/ Verifying : ibm-fasp.io-gateway-1.0.1-1.x86_64 1/1ĭefault configuration files: /etc/fasp.ioĭocumentation: /usr/share/fasp.io-gateway I got all these steps from there -ĭownload ASP_FASP.IO_GW_V1.0.1_LNX_EN.zip from IBM site and keep it available in the serverĮxample: sudo unzip ASP_FASP.IO_GW_V1.0.1_LNX_EN.zipĮxample: sudo yum install. Step by step process for installing Aspera Fasp.io gatewayįollow the IBM page.
