FASP Transfer Plugin

This action plug-in provides the ability to initiate a server to server transfer using Aspera's FASP protocol.

Saved Parameters Description

Name: The name used to identify a saved FaspTransfer configured instance.
Comments: Some comments about this saved FaspTransfer configured instance.

This action allows to start and monitor a Fasp Transfer using a remote Aspera node.

Note: This plugin uses Aspera Central to start and control the transfer, so Aspera Central should listen and accept connections from external node. For releases before 3.4 the Aspera Node needs to have a Reliable Query API enabled in aspera.conf. Also, reliable API must be enabled on the Aspera Server being polled, and the IP address polling must be enabled as shown below for <central_server>.

<address>0.0.0.0</address>
<port>40001</port>
<persistent_store>enable</persistent_store>
</central_server>

This works for Enterprise Server, Connect Server, Faspex Server and Point to Point. For complete information regarding setup of the above servers, and understanding of the Central SOAP API, please visit the Aspera Developer Network

In order to retrieve the list of file(s) that failed to transfer, node user and password should be provided, and the Ascp verison should be 3.6.1 or above.

Inputs Description

The list of inputs depends on the configuration of the FaspTransfer action template.

Outputs Description

Job_ID: The ID of the Fasp Session
Transfer_Stats: The Fasp Session statistics
Transferred_File_list: The files transfered by this session
Transferred_Files_md5: For each file, the computed MD5

Job Definitions

The data types that are described in this section are used in the XML order description format for Aspera.IScpTransfer Job Types.

Job Order Description (Parameters)