Step by step process for installing Aspera Fasp.io gateway

Step by step process for installing Aspera Fasp.io gateway Follow the IBM page. I got all these steps from there - https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/com.ibm.mq.con.doc/aspera_def_unixlinux.htm Download ASP_FASP.IO_GW_V1.0.1_LNX_EN.zip from IBM site and keep it available in the server Example: /opt/softwares/Aspera/ Unzip the file. Example: sudo unzip ASP_FASP.IO_GW_V1.0.1_LNX_EN.zip Use rpm file with yum install. Example: sudo yum install ./ibm-fasp.io-gateway-1.0.1-1.x86_64.rpm ........ ....... Installed size: 8.8 M Is this ok [y/d/N]: y Then it looks like the below. Running transaction test Transaction test succeeded Running transaction Installing : ibm-fasp.io-gateway-1.0.1-1.x86_64 1/1 Verifying : ibm-fasp.io-gateway-1.0.1-1.x86_64 1/1 Installed: ibm-fasp.io-gateway.x86_64 0:1.0.1-1 Complete! _________________________________________________________________________________________ Location of installed files: Executable: /usr/bin Default configuration files: /etc/fasp.io Documentation: /usr/share/fasp.io-gateway SystemD startup file: /etc/systemd/system/fasp.io-gateway.service ************************************************************************************************** Copied the below example from IBM Site only Example This example defines an Aspera gateway connection on two machines running Linux. The configuration is as follows: The IP address of the local gateway machine is 9.20.193.107. The IP address of the remote gateway machine is 9.20.192.115. The local queue manager is running on a machine with IP address 9.20.121.5. The remote queue manager is running on a machine with IP address 9.20.121.25. Both queue managers are listening on port 1414. 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). 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). Define an Aspera gateway connection on the local gateway machine: Install the Aspera gateway: rpm -ivh ibm-fasp.io-gateway-1.0.0_qa_48-1.x86_64.rpm Modify the gateway.toml file in the /etc/fasp.io directory that was created by the install. Edit it to set the local gateway definitions. [[bridge]] name = "Outbound" [bridge.local] protocol = "tcp" host = "9.20.193.107" port = 1500 [bridge.forward] protocol = "fasp" host = "9.20.192.115" port = 1600 [[bridge]] name = "Inbound" [bridge.local] protocol = "fasp" host = "9.20.193.107" port = 1600 [bridge.forward] protocol = "tcp" host = "9.20.121.5" port = 1414 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. Edit it to set the remote gateway definitions: [[bridge]] name = "Outbound" [bridge.local] protocol = "tcp" host = "9.20.192.115" port = 1500 [bridge.forward] protocol = "fasp" host = "9.20.193.107" port = 1600 [[bridge]] name = "Inbound" [bridge.local] protocol = "fasp" host = "9.20.192.115" port = 1600 [bridge.forward] protocol = "tcp" host = "9.20.121.25" port = 1414 At each end of the connection, change the channel definition to connect to the port that the local gateway is listening on. Change the queue manager channel on the local queue manager to connect to the local Aspera gateway using conname 9.20.193.107(1500). Change the queue manager channel on the remote queue manager to connect to the remote Aspera gateway using conname 9.20.192.115(1500). Start the local gateway by running the following command on the local gateway machine: systemctl start fasp.io-gatewayCopy code Start the remote gateway by running the following command on the remote gateway machine: systemctl start fasp.io-gatewayCopy code Restart the channels. ************************************************************************************************************* In case if Queue manager and FASP gateway are on the same server. The configuration may look like below. Here local queue manager and FASP are on the same machine - 192.168.1.107. Similarly the remote FASP gateway is 192.168.1.108. [[bridge]] name = "Outbound" #connection from the local queue manager to the local fasp gateway [bridge.local] protocol = "tcp" host = "192.168.1.107" port = 1500 #from the local fasp gateway to the remote fasp gateway [bridge.forward] protocol = "fasp" host = "192.168.1.108" port = 1600 [[bridge]] name = "Inbound" #the connection from the remote fasp gateway to the local fasp gateway [bridge.local] protocol = "fasp" host = "192.168.1.107" port = 1600 #from the local gateway to the local queue manager. [bridge.forward] protocol = "tcp" host = "192.168.1.107" port = 1414 [[bridge]] name = "Outbound" [bridge.local] protocol = "tcp" host = "192.168.1.108" port = 1500 [bridge.forward] protocol = "fasp" host = "192.168.1.107" port = 1600 [[bridge]] name = "Inbound" [bridge.local] protocol = "fasp" host = "192.168.1.108" port = 1600 [bridge.forward] protocol = "tcp" host = "192.168.1.108" port = 1414