The Reliable Transfer Service (RFT) Service implementation in GT 4.1.0 uses standard SOAP messages over HTTP to submit and manage a set of 3rd party GridFTP transfers and deletion of files and directories using GridFTP. The service also provides an interface to control various transfer parameters of the GridFTP control channel like TCP buffer size, parallel streams, DCAU etc. The user creates a RFT resource by submitting a Transfer Request (consisting of a set of third-party gridftp transfers) to the RFT Factory service. The resource is created after the user is properly authorized and authenticated. RFT service implementation exposes operations to control and manage the transfers (the resource). The resource the user created exposes the state of the transfer as a resource property to which the user can either subscribe for changes or poll for the changes in state periodically using standard WS-RF command line clients and other resource properties.

New features new in GT 4.1.0

The following changes have occurred for RFT since the last stable release, 4.0.2:

No interface changes happened since 4.2 execpt for the addition a new schema file for Apache Derby database that is setup automatically when RFT is deployed

A new command-line client written in C is added to the distribution

The configured maximum allowed active transfers constraint is not enforced. For more details please look at the bug report.

RFT depends on the following GT components:

RFT depends on the following 3rd party software:

Tested platforms for RFT:

Tested containers for RFT:

Protocol changes since GT 4.0.2

API changes since GT 4.0.2

Exception changes since GT 4.0.2

Schema changes since GT 4.0.2

Associated standards for RFT:

See Reliable File Transfer (RFT) Service for more information about this component.