IN THIS ARTICLE:
Aspera Faspex Server is a file exchange web application built upon Aspera Enterprise Server as a centralized transfer solution. In order to run, Aspera Faspex Server needs two license files: one license for the web application and one license for the Aspera Enterprise Server.
Since Faspex version 2.6 it is possible to run the Faspex web application on a separate server from the transfer server (Aspera Enterprise Server). All Faspex licensees are entitled to run a single separate transfer server.
Those who license Faspex for High Availability (HA) can run the Faspex web application with a "cluster" of transfer servers. For more information about this option please contact your sales account manager.
Where are licenses on a Faspex server?
The Faspex web application license (also called the "Faspex User" license) can be found in the following folder:
- Windows: C:\Program Files (x86)\Aspera\Faspex\config
- Linux: /opt/aspera/faspex/config
- Windows: C:\Program Files (x86)\Aspera\Enterprise Server\etc\aspera-license
- Linux: /opt/aspera/etc/aspera-license
How do I install a Faspex license?
For Faspex versions 3.0 and later, you install the license on the Faspex web interface. On your Faspex web page, click on the Server tab of the main navigation menu. On the Configuration tab, click License, and from here you will be able to upload your license or paste its contents to install it.
For Faspex versions prior to 3.0, you will have to place your license file into the folder listed in the previous section to install it.
What is the naming convention for licenses used with Faspex?
Faspex Application / User license for Faspex 1.x to Faspex 2.6.0
The Faspex application or user license file has one of the following file naming conventions:
where ID is the license id for this Faspex web application.
During an evaluation the license normally also includes eval in the name, for example: aspera.faspex.users.21609.eval.license
Faspex Application / User license for Faspex 2.6.5+
The license file provided has the following file naming convention:
where ID is the license ID for this Faspex Web Application.NOTE: After Faspex 2.6.5 the Faspex application license and the Faspex Enterprise Server license have the same extension. This means for Faspex versions prior to 3.0 both licenses must NOT be placed in the faspex/config folder. If this happens Faspex will *not* see a valid license and will not let users login.
For Aspera Enterprise Server
- ID-EntSrv-Faspex-BANDWIDTH.aspera-license (*this is the current naming convention)
ascp -DD -A