Follow instructions provided by GT 4.1.1 System Administrator's Guide and Installing GT 4.1.1 in order to install the DRS from one of the available binary bundles of the Globus Toolkit.

Once you have unpackaged the binary bundle, the following commands may be used to install DRS:

% ./configure --prefix=$GLOBUS_LOCATION --enable-rls --enable-drs
% make
% make install
        

DRS is not installed as part of the default source install. In order to install DRS, you will need to ensure that RLS is also installed as part of the build by reviewing its installation procedures. Along with RLS configure settings (e.g., ODBC related settings) the --enable-drs flag is required as part of the configuration step.

The following commands will install the DRS (optionally you may use the "drs" make target to build only DRS and its requirements:

% ./configure --prefix=/path/to/install --with-iodbc-includes=/path/to/iodbc/include --with-iodbc-libs=/path/to/iodbc/lib --enable-rls --enable-drs
% make [drs]
% make install
        

Additionally, you may access the DRS from the Globus Toolkit CVS repository. You may deploy the 4.0.x DRS on top of an existing GT 4.0.x installation using the globus_4_0_branch tag. You may deploy the 4.1.x DRS on top of an existing GT 4.1.x installation using trunk.

The following example instructions will only work given the presence of an existing GT installation with all DRS dependencies. The best way to establish such an environment is to first follow the basic installation instructions and subsequently use the following instructions to obtain the latest updates from the CVS branch. Note the use of the globus_4_0_branch tag depends on whether you are interested in updates from the maintenance branch or the development trunk.

% setenv GLOBUS_LOCATION /path/to/existing/gt4xx/install/
% setenv CVSROOT :pserver:anonymous@cvs.globus.org:/home/globdev/CVS/globus-packages
% cvs co -r globus_4_0_branch ws-replica/
% cd ws-replica/replicator/
% ant deploy
        

To learn more about general instructions regarding GT CVS access, see Remote CVS Access.

The DRS requires certain JNDI settings to be properly configured. The installed JNDI configuration file may be found at $GLOBUS_LOCATION/etc/globus_wsrf_replicator/jndi-config.xml. To view the default configuration file (shipped with the GT 4.1.1 release) from the Globus CVS repository click here.

The settings are structured as name-value pairs. For example:

    <parameter>
      <name>defaultIndexUrl</name>
      <value>rls://127.0.0.1:39281</value>
    </parameter>
    

The following settings must be properly configured:

The service configuration files such as the JNDI configuration file,jndi-config.xml, and the Web service deployment descriptor, server-config.wsdd, located in the $GLOBUS_LOCATION/etc/globus_wsrf_replicator directory, contain sensitive information such as database username and password. It is important to ensure that these files are readable only by the system administrator that is responsible for the container. During deployment, the permissions on these files are adjusted automatically, however, you should verify the permissions to ensure that they have been correctly set for your specific platform.

Creating a Replicator requires that the user supply a delegated credential to the DRS during the initial creation request. The service retrieves the delegated credential from the Delegation Service and stores it on the file system. As part of the DRS configuration (see installation and configuration instructions), the user selects a directory to use for storage of delegated credentials. The default setting is for the DRS to store the file in the system's designated temporary directory (e.g., /tmp on many platforms). The service sets the permissions on the temporary file such that it can only be accessed by the user account used to run the container.