Here you will learn how to develop and deploy an Aspera Embedded Client.
To get your application to act as a client for FASP transfers you will need the following files, all of these files are found in the Aspera Redistributable Package:
- Aspera Transfer Engine (ascp or ascp.exe) - This is used to initiate the transfers.
- Aspera Configuration File (aspera.conf) - This is an XML based file that contains the configuration for the server.
- Aspera License File (aspera-license) - This is the license file that should be used for your setup
- Dependencies - This is optional and if needed would be included with the transfer engine found in the Redistributable Package.
The license file that is available in the Redistributable Package is a free Aspera Connect license. To use this license you need an Aspera Connect server license on your Aspera server. If you intend to use Aspera Enterprise server license on the server, you need to purchase the client licenses separately from Aspera. Please contact your Aspera Account Manager for more information.
Now that you have your needed files you need to package and deploy all of the files to the target machine along with your custom application; you can copy these files to any directory, however, it is imperative that they are all in the same directory.
To configure the path to the Aspera transfer engine in your FASP Manager environment you should call one of the following methods (depending on what language you are using), if you do not FASP Manager may be able to detect and use the ascp transfer engine at runtime, however, by setting it manually you ensure it will run successfully and avoid ambiguity if multiple copies of ascp are installed.
For example, you could run the following command in C# or Java to set the path to C:\\Program Files\Aspera\Enterprise Server\bin\ascp.exe.
Environment.setFasp2ScpPath("C:\\Program Files\\Aspera\\Enterprise Server\\bin\\ascp.exe");