- Doc Structure
- A Globus Primer
- Globus Is Modular!
- Installing GT
- Platform Notes
- Migrating from GT2
- Migrating from GT3
- PDF version
- Best Practices
- Coding Guidelines
- API docs
- Public Interfaces
- Resource Properties
- Performance Studies
Table of Contents
The Reliable Transfer Service (RFT) Service implementation in GT 4.1.2 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.
Features new in GT 4.1.2
- No new features since GT 3.9.5.
- Delete files: Delete a set of files/directories on a GridFTP server.
- Exponential Backoff: Configurable exponential back off before a failed transfer is retried.
- Transfer All or None: If this option is set and one of the transfers in the request fails, RFT will stop transferring the remainder of the request and delete the files that were already transferred successfully.
- Transfer Permissions: File permissions are restored at the destination once the file is transfered successfully. This can be configured to throw a fatal error or a transient error depending on whether the GridFTP server supports the MLST command.
- Configurable number of concurrent transfers per container and per request.
- Better error reporting and faults.
- Database purge of the request and transfers after life time expiration.
- Cumulative (aggregate ) Resource Properties on the factory provide some statistical information.
- One status Resource Property for the entire transfer.
- Recursive directory transfers and deletes.
- Parallel streams.
- TCP Buffer Size.
- Third-party directory transfers, file transfers and deletes.
- Data channel authentication (DCAU).
- NoTPT option.
- Different subject names for source and destination GridFTP servers for the authorization mechanism.
- Support for binary/ascii type of transfers.
- Configurable number of retries for failed transfers per request.
- Block Size in bytes.
The following changes have occurred for RFT since the last stable release, 4.0:
The following problems and limitations are known to exist for RFT at the time of the 4.1.2 release:
- 3121 - The configured maximum allowed active transfers constraint is not enforced.
RFT depends on the following GT components:
- Java WS Core
- WS Authentication and Authorization
- Delegation Service
- Service Groups
- MDS useful RP
RFT depends on the following 3rd party software:
- PostgreSQL 7.1 or later. Not tested with 8.0 yet.
Tested platforms for RFT:
- Fedora Core 1 i686
- Fedora Core 3 i686
- RedHat 7.3 i686
- RedHat 9 x86
- Debian Sarge x86
- Debian 3.1 i686
Mac OS X
- Mac OS X 10.3, 10.4
Tested containers for RFT:
- Java WS Core container
- Tomcat 5.0.30
Protocol changes since GT 4.0
- Added All or None option, maximum attempts, and finishBy to the transfer request
- Not backwards compatible with the OGSI version
API changes since GT 4.0
Exception changes since GT 4.0
Schema changes since GT 4.0
- WSDL changes to work with the new Java WS Core
See Reliable File Transfer (RFT) Service for more information about this component.