Faspex Installation Scenarios

Overview

Faspex is a file exchange application built upon IBM Aspera Enterprise Server and other Aspera transfer products as a centralized transfer solution. In order to make transfers, Faspex communicates with a node through the Node API. The Node API is a daemon on the transfer server that offers REST-inspired file operations and a transfer management API.

There are three main ways to install Faspex.

Use Case 1: Installing Faspex with the Transfer Server on the Local Workstation

The simplest use case is to install both Faspex and the transfer server on the same workstation. When installing Faspex on the same workstation as a transfer server, Faspex automatically configures the local node's aspera.conf configuration file and sets up a Node API user to communicate with the Node API. During installation, you can also choose to perform a streamlined installation which allows Faspex to configure advanced options to Faspex defaults. This streamlined installation is not available when the transfer server is on a remote workstation.

For instructions, see Installing Faspex with a Local Node.

Use Case 2: Installing Faspex with the Transfer Server on a Remote Workstation

When installing Faspex on a machine without a transfer server, you must configure a remote transfer node for use with Faspex and connect that node to Faspex during the installation process.

For instructions, see Installing Faspex with a Local Node.

Use Case 3: Installing Faspex Programmatically with a Setup File

It is possible to automate the installation of Faspex by using setup files to define configuration options that are manually set during a typical installation. You must first use the asctl command to generate a setup file with the desired configuration information. After you have created the setup files, you can use them to install Faspex.

For instructions, see Installing Faspex with a Setup File.