Configuring a Remote Server in Faspex

Faspex communicates with a transfer server product (IBM Aspera Enterprise Server or IBM Aspera Connect Server) using the Node API, a daemon on the transfer server that offers REST-inspired file operations and a transfer management API. A local, remote, or cloud system installed with a transfer server is called an Aspera node. Faspex can access a local node or a transfer node remotely via the Node API.

You can add multiple nodes to Faspex from the File Storage page (go to Server > File Storage). Faspex lists connected nodes and configured file storage on the File Storage Page. On a fresh install, the default Faspex transfer server, localhost, is the only server listed, and its default storage directory, packages, is the default inbox destination.

To add a remote server to Faspex, you must first configure the node machine. For more information, see Configuring a Remote Transfer Node for Faspex.

Follow the instructions below to add a configured node to Faspex.

  1. Go to Server > File Storage to configure access to the node that manages your Aspera transfers. To add another file storage, click the Add New Node link.
  2. Configure the following file storage details:
    Field Description
    Name Unique name to identify the remote node.
    Use SSL To encrypt the connection to the node using SSL, enable this box.
    Verify SSL Certificate To verify the SSL certificate, enable this box. For more information on installing a valid SSL certificate, see Working With SSL.
    Host The node's hostname or IP address.
    To avoid connectivity problems, do not specify a hostname that contains underscores.
    Port The Node API port number. By default, the port is 9092.
    Username The Node API username on the node machine.
    Password The Node API password on the node machine.
    Storage type Specify whether you are connecting to a node using Windows Azure or Windows Azure SAS storage. If you are not connecting to such a node, choose Default.
    Note: For more information on adding an Azure node, see Adding Azure Node to File Storage.
  3. Test the node connection by selecting Test Connection.
    If the connection is successful, Faspex displays: "Connection succeeded!" Otherwise, Faspex displays an error. For more information about troubleshooting the connection, see Troubleshooting File Storage Errors.
  4. Optional: Expand the Advanced Configuration section to designate a primary transfer address or configure a secondary IP address to allow users to start transfers from different IP addresses.
  5. Create the node.
    • Select Create to simply create your node.
    • Select Create and Add File Storage to create your node and proceed to add file storage to your node. For more information on file storage and instructions on how to add it to your node, see Adding File Storage on your Remote Server.