Installing HTTP Gateway

Install HTTP Gateway on any server running a supported OS that can communicate with both the clients and the desired IBM Aspera High-Speed Transfer Server (HSTS) nodes.

About this task

While you can install HTTP Gateway on the same server as the HSTS nodes (if the servers has enough resources), IBM Aspera recommends running HTTP Gateway on a separate server. Installing on separate servers allows you to dedicate resources and to deploy the HTTP Gateway hosts close to clients.

Procedure

  1. Before installing HTTP Gateway, review the system requirements in the HTTP Gateway release notes.
  2. Download the HTTP Gateway RPM package.
  3. Install HTTP Gateway: 
    # rpm -Uvh ibm-aspera-httpgateway-version.x86.64.rpm
  4. Create the gatewayconfig.properties to configure HTTP Gateway settings.
    Copy the default.properties file as a base for the gatewayconfig.properties.
    # cp /opt/aspera/httpgateway/config/default.properties /opt/aspera/httpgateway/config/gatewayconfig.properties
    Note:
    • The gatewayconfig.properties file overrides the settings in the config/default.properties.
    • The gatewayconfig.properties must live in a config folder at the same level as the aspera-httpgateway binary.
    • The gatewayconfig.properties file is preserved on upgrade.
  5. Edit the gatewayconfig.properties file.

    IBM Aspera recommends securing your system by providing your own trusted root certificates for HTTPS. For more information, see Configuring HTTP Gateway to Use HTTPS Scheme.

    For more information on the gatewayconfig.properties options, see gatewayconfig.properties Reference.

  6. Start the aspera_httpgateway service: 
    # service aspera_httpgateway start
    For a systemd OS, run:
    # systemctl start aspera_httpgateway