Transfer with Aspera HTTP Gateway instead of Aspera Connect

Edit online

You can use your IBM Aspera HTTP Gateway as a transfer client for Aspera on Cloud. This configuration supports users who cannot install the IBM Aspera Connect transfer client. Use this procedure to configure your Aspera on Cloud organization to use your Aspera HTTP Gateway.

Users who can install Aspera Connect can and should continue to use it, even as others in the organization use the HTTP Gateway for transfers. Aspera Connect transfers are typically faster than Aspera HTTP Gateway transfers.

The Aspera HTTP Gateway is a standalone product that uses both HTTP/S and Aspera FASP to complete file transfers. To install and configure the Aspera HTTP Gateway, see the IBM Aspera HTTP Gateway Admin Guide.

Once you configure your Aspera HTTP Gateway, you can point your Aspera on Cloud organization to it. Enabling the Gateway ensures that all Aspera on Cloud users can transfer.

Best practices and limitations

Edit online
Best practices
  • IBM Aspera highly recommends deploying HTTP Gateway as close as possible to end users. Gateway proximity mitigates the speed degradation inherent in HTTP/HTTPS transfers over distance.
  • Users who can install and use the Aspera Connect transfer client should do so. Transfers using Aspera Connect are generally faster, so Connect remains the preferred transfer method.

Limitations

For transfers using the HTTP Gateway:
  • To upload a folder, you must either:
    • Archive the folder as a .zip or other archive file type.
    • Open the folder and upload the files in it.
    When you try to upload a folder, Aspera on Cloud displays an explanatory notice, then opens your Finder or Explorer so you can select one or more files for upload.
  • When you download a folder or download multiple files in a single transfer, Aspera on Cloud automatically archives the folder or the files as a .zip file and then downloads the .zip file.
  • Aspera on Cloud does not show HTTP Gateway transfers in the Transfer monitor. Use your browser download manager to track downloads.
  • Do not close the Aspera on Cloud application browser tab until the upload completes. You can open a new tab or switch to a different open tab on your browser.
  • You cannot resume an interrupted HTTP Gateway transfer. You must start the transfer over.
  • You cannot upload empty files or folders.
  • You cannot download empty folders.

Enable Aspera HTTP Gateway

Edit online
  1. Go to Admin > Organization > Aspera HTTP Gateway > Configuration.
  2. Set the Enable toggle to On.
  3. Paste the URL of your Aspera HTTP Gateway into the following field.
    For example, https://http-gateway.mycompany.com/aspera/http-gwy/v1.
  4. Click Test connection.
    A success notification displays when the connection is established.
    If the connection test fails, check the URL for accuracy and verify proper network configuration. Then click Test connection again.
  5. Click Save.
  6. For users who cannot install Aspera Connect, disable Connect and the Connect installation prompt:
    1. Click Aspera Connect configuration.
    2. Select the users and groups who cannot install Aspera Connect; Aspera on Cloud disables Connect for these users and will not prompt them to install Connect.
      Individual users can disable Aspera Connect by using the toggle at the bottom of the transfer monitor panel; the user setting overrides the Admin setting.