Configuration overview

PostgreSQL (Version 7.1 or greater ) needs to be installed and configured  for RFT to work. The instructions on how to install/configure postgresql can be found here (add a link to instuctions here).
  1. Install Postgresql. Configure the postmaster daemon so that it accepts TCP connections. This can be done by adding -o "-i" switch to postmaster script.
  2. To create the database that is used for RFT, run:
    createdb rftDatabase
  3. To populate the RFT database with appropriate schemas, run:
    psql -d rftDatabase -f $GLOBUS_LOCATION/share/globus_wsrf_rft/rft_schema.sql

    Now that you have created a database to store RFT's state, the following steps configure RFT to find the database:
  4. Open $GLOBUS_LOCATION/etc/globus_wsrf_rft/jndi-config.xml
  5. Find the dbConfiguration section under ReliableFileTransferService <service> section.
  6. Change the connectionString to point to the machine on which you installed Postgres and name of the database you used in step 2.
    If you installed Postgres on the same machine as your Globus install, the default should work fine for you.
  7. Change the userName to the name of the user who owns/created the database and do the same for the password. (It also depends on how you configured your database.)
  8. Don't worry about the other parameters in that section. The defaults should work fine for now.
  9. Edit the configuration section under ReliableFileTransferService. There are two values that can be edited in this section.
    • backOff  : Time in seconds you want RFT to backoff before a failed transfer is retried by RFT. Default should work fine for now.
    • maxActiveAllowed:  This is the number of transfers the container can do at given point. Default should be fine for now.

Frequent configuration problems

Problem: If RFT is not configured properly to talk to a PostgreSQL database, you will see this message displayed on the console when you start the container : 

"Error creating RFT Home: Failed to connect to database ... 
Until this is corrected all RFT request will fail and all GRAM jobs that require staging will fail".

Solution: Usual mistake is Postmaster is not accepting TCP connections which  means that you have to restart Postmaster with -i option  ( see step 1)

Syntax of the interface

The security configuration of the service can be modifying the security descriptor. It allows for configuring in the credentials that will be used by the service, type of authentication and authorization that needs to be enforced. By default, the following security configuration is installed:

  • Credentials set for use by container is used. If that is not specified, default credentials are used.
  • GSI Secure conversation authentication is enforced for all methods.

Note: Changing required authentication and authorization method will require suitable changes to the clients that contact this service.

To alter security descriptor configuration refer to Security Descriptors. The file to be altered is $GLOBUS_LOCATION/etc/globus_wsrf_rft/security-config.xml