Working With Remote Servers

Before configuring IBM Aspera Faspex on Demand to communicate with a remote transfer server, it is important to understand how it is able to do so. IBM Aspera Enterprise Server or IBM Aspera Connect Server v3.0+ features the Node API, a daemon that offers REST-inspired file operations and a transfer management API. When you install Enterprise Server or Connect Server 3.0+ on a local/remote system or EC2 instance, it becomes an Aspera "node." Faspex can be installed on the transfer node, or it can access the transfer node remotely via the Node API. This topic explains how to configure Faspex to access a remote transfer node and directory shares.

First, make sure that you have Enterprise Server or Connect Server 3.0+ installed on the remote machine. To continue, make sure you have the following information at hand:

• The node computer's hostname or IP address, along with a port and path (if applicable).
• The node API username and password, which you created when you set up Enterprise Server on your node machine.