Configuring for Faspex

The steps below describe configuring as the transfer server for IBM Aspera Faspex.

  1. Install Enterprise/Connect Server.
    If you haven't already, follow the steps in Installation and Upgrades to install .

    The transfer server can be set up in either of the following configurations:

    • locally, on the same host as Faspex
    • remotely, on a separate host
    Note: For a local setup, most configuration is taken care of automatically when Faspex is installed in a later step. For this reason, Enterprise Server/Connect Server should be installed first.

    All steps must be performed with administrator permissions.

  2. Create the system user on the transfer-server host.

    The system user authenticates the actual ascp transfer and must be an operating system account. To create a new system user faspex on your Windows system, go to Control Panel > User Accounts. After adding the faspex user, change the user's password.

  3. Create and configure the Faspex packages directory.

    Create the directory C:\faspex_packages.

  4. Add the faspex user to Enterprise/Connect Server.
    Launch the desktop application and click Configuration.
    Click the Configuration.

    In Server Configuration, open the Users tab. Then click the Add user button.


    Add the test user.

    In the Add User dialog that appears, fill in the name faspex and click OK. The faspex user is added to the user list.

    To specify a docroot, select faspex in the user list and click the Docroot tab in the right panel. For the Absolute Path setting, select the Override box, and under Effective Value fill in the following:

    C:\faspex_packages

    For the read, write, and browse settings, select the Override boxes and select true.

    You can also add and configure the faspex user for by modifying aspera.conf, instead of using the application GUI. For details, see Setting Up Users.

  5. Configure server settings.
    In a Command Prompt window, run the following commands to set the server name with the name or IP address of your server, enable persistent storage (persistent storage is enabled by default), and ensure that the faspex user has browse privileges:
    > asconfigurator -x "set_server_data;server_name,server_ip_or_name"
    > asconfigurator -x "set_central_server_data;persistent_store,enable"
    > asconfigurator -x "set_user_data;username,faspex;dir_allowed,true"
  6. Restart Aspera Central and Aspera NodeD services to activate your changes.

    You can restart the Aspera Central from the Computer Management window. Go to Control Panel > Administrative Tools > Computer Management > Services and Applications > Services, click Aspera Central, and click Restart.

    Go to Control Panel > Administrative Tools > Computer Management > Services and Applications > Services, click Aspera NodeD, and click Restart.

  7. Verify that you have a valid Faspex-enabled license installed.
    • From the command line: In a Command Prompt window, run the following command and inspect the output, which lists the enabled settings:
      > ascp -A
      Enabled settings: connect, mobile, cargo, node, proxy, http_fallback_server, 
      group_configuration, shared_endpoints, desktop_gui

      If the list includes connect and http_fallback_server, you have a Faspex-enabled server license.

    • In the GUI: Click Tools > License and if Connect Clients Enabled and Http Fallback Server Enabled are set to Yes, you have a Faspex-enabled license.

    If you update your license (see Updating the Product License), you must reload the asperanoded service afterwards. Reload the asperanoded service by running the following command:

    > asnodeadmin --reload
  8. Set up the node user.
    Associate the transfer user faspex with a node username and password by running the asnodeadmin command, as in the following example in which node-admin is the node user, s3cur3_p433 is the node user's password, and faspex is the system user. Then run asnodeadmin again to reload asperanoded.
    > asnodeadmin -a -u node-admin -p s3cur3_p433 -x faspex
    > asnodeadmin.exe --reload 
  9. Install the Connect key.
    Locate your Connect key:

    C:\Program Files [(x86)]\Aspera\Enterprise Server\var\aspera_tokenauth_id_rsa.pub

    Create an .ssh folder (if it does not already exist) in the Faspex user's home folder: C:\Users\faspex\.ssh . Use a text editor to create (or modify) the authorized_keys file, with no file extension, in the .ssh folder. Add the faspex user's key string into this file and save it. Note that some text editors add a .txt extension to the filename automatically. Be sure to remove the extension if it was added to the filename.

  10. Ensure the firewall is set up correctly on your transfer server.
    For details, see Configuring the Firewall.
  11. Configure your remote transfer server in the Faspex Web GUI.
    Follow the instructions in the Aspera Faspex Admin Guide: Transfer Server for configuring your remote transfer server in the Faspex Web GUI underServer > File Storage.