Product Setup

Install the IBM Aspera transfer product and set up your computer for FASP file transfers.

Important: If this is a product upgrade, ensure that you have reviewed all prerequisites detailed under "Before Upgrading."

IBM Aspera Connect Server is a web-based file server that enables file access through a browser, and transfers files using the IBM Aspera Connect Browser Plug-in. Additionally, you can set up HTTP Fallback to establish HTTP- or HTTPS-based file transfers with clients that don't have FASP connectivity.

To install Connect Server, log into your computer with root permissions, and follow the steps below.

  1. Download the IBM Aspera product installer.

    Download the installer from the link below. Use the credentials provided to your organization by Aspera to access:

    http://asperasoft.com/en/downloads/4

    If you need help determining your firm's access credentials, contact Technical Support.

  2. For product upgrades, ensure you have prepared your machine to upgrade to a newer version.

    Although the installer for Aspera Connect Server performs your upgrade automatically, Aspera highly recommends completing the tasks identified in the topic Before Upgrading. If you do not follow these steps, you risk installation errors or losing your former configuration settings.

  3. Run the installer

    When downloaded, run the installer using the following commands and with the proper administrative permissions. Replace the file name accordingly.

    OS Commands
    RedHat
    $ rpm -Uvh aspera-entsrv-version.rpm 
    Debian
    $ dpkg -i aspera-entsrv-version.deb
  4. Install the license.

    The following table describes two ways to install the license: through the GUI or via command line.

    Method Instructions
    GUI To install the license via the GUI, execute asperascp in a Terminal (as a root user) to launch the application. If this is a fresh install, an Enter License window appears. You may click the Import License File and select the license file, or Paste License Text to copy-and-paste the license file's content. When finished, the license information will appear in the window. Verify that it is correct and click Close.
    The Enter License window.
    Terminal To install the license from the command line, create the following file and paste your license key string into it:
    /opt/aspera/etc/aspera-license
    When finished, save and close the file. Use this command to verify the license info:
    $ ascp -A

    If you are updating your product license after the installation, see Updating the Product License.

  5. Review or update OpenSSH authentication methods.

    Open your SSH Server configuration file with a text editor:

    /etc/ssh/sshd_config

    To allow public key authentication, set PubkeyAuthentication yes. To allow password authentication, set PasswordAuthentication yes, for example:

    ...
    PubkeyAuthentication yes
    PasswordAuthentication yes
    ...

    When modified, run the following to reload SSH:

    RedHat
    $ sudo service sshd restart
    Debian
    $ sudo /etc/init.d/ssh restart

    To further review your SSH Server's configuration to strengthen security, see Securing your SSH Server.

  6. Convert the old aspera.conf file manually (necessary only when upgrading from product version 2.2 or earlier)

    For product versions 2.5+, the docroot settings have been moved to the Aspera configuration file, aspera.conf. When upgrading from product version 2.2 or earlier, the installer converts your old configuration files to the new format, using a "strict" method. If the old aspera.conf file has errors or unrecognized directives, the conversion will fail. To review the errors, run a strict conversion manually. Change aspera.conf's path if it is not in the default location.

    $ cd /opt/aspera/etc
    $ sudo asconfigurator -T -F convert_conf_V1_data ./aspera.conf

    If an error occurs during the conversion, use the relaxed conversion method:

    $ cd /opt/aspera/etc
    $ sudo asconfigurator -F convert_conf_V1_data ./aspera.conf 
  7. (For upgrades) Check aspera.conf for errors

    When upgrading your Aspera product to a newer version, it is recommended that you check the aspera.conf configuration file for errors. Run the following command in a terminal window to validate aspera.conf:

    $ /opt/aspera/bin/asuserdata -v 
  8. Set up your new Connect Server's web UI (or verify your web UI settings after an upgrade).

    At this point, your IBM Aspera transfer product is installed; however additional steps are required to configure the web UI. For information on configuring the web UI, see "Connect Server Web UI Setup".

    Important: On some Fedora systems, there is a missing perl-Digest-MD5 dependency that goes unreported when Connect Server is installed. Its absence only becomes visible when you launch a Connect Server browser and get a 500 error logged as "Can't locate Digest/MD5.pm ..." To prevent this error, ensure that the perl-Digest-MD5 module is installed with Connect Server by running the following command:
    $ sudo yum install perl-Digest-MD5
    Important: When upgrading from Connect Server versions older than 3.0, system-level security settings are not preserved and must be reconfigured. For instructions on enabling or disabling system-level security, see "Configuring Apache" (second-to-last step).