Table of Contents
This guide contains advanced configuration information for system administrators working with the Data Replication Service (DRS). It provides references to information on procedures typically performed by system administrators, including installing, configuring, deploying, and testing the installation.
![[Important]](../../../../../docbook-images/important.gif) | Important |
|---|---|
This information is in addition to the basic Globus Toolkit prerequisite, overview, installation, security configuration instructions in the GT 4.0 System Administrator's Guide. Read through this guide before continuing! |
DRS is not installed as part of the standard install. In order to install DRS, you will need to ensure that RLS is also installed as part of the build by setting GLOBUS_IODBC_PATH or configuring with the --with-iodbc flag. Also, the --enable-drs flag is required as part of the configuration step. The following commands will install the DRS.
% ./configure --prefix=/path/to/install --with-iodbc=/path/to/iodbcdir --enable-drs % make % make install
| Important |
|---|---|
The DRS depends on the Globus RLS. In order for the "make" command above to build
and install the RLS, you must follow the basic installation instructions for GT 4.0 as noted previously.
Installation of the RLS requires that the |
Additionally, you may access the 4.0.1 branch of DRS from the Globus Toolkit CVS repository. You may deploy the 4.0.1 DRS on top of an existing GT 4.0.0 installation as well as a GT 4.0.1 installation. The following instructions will only work given the presence of an existing GT 4.0.0 or GT 4.0.1 installation with all DRS dependencies. The best way to establish such an environment is to first follow the above instructions and subsequently use the following instructions to obtain the latest updates from the CVS branch.
% setenv GLOBUS_LOCATION /path/to/existing/gt40x/install/ % setenv CVSROOT :pserver:[email protected]:/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.
This information is in addition to the basic configuration instructions in the GT4.0 System Administrator's Guide. Aside from the basic configuration of GT 4.0, please review the following instructions:
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.0.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:
proxyfileDir: the directory that you would like the DRS to temporarily store user proxies. No setting is necessary. This value may be empty.requestfileDir: the directory that you would like the DRS to temporarily store request files. No setting is necessary. This value may be empty.defaultIndexUrl: the connection URL for your installation of RLS running as a RLI service.defaultRegistrationUrl: the connection URL for your installation of RLS running as a LRC service.defaultReliableTransferUrl: the connection URL for your installation of the RFT ReliableFileTransferFactoryService.proxyfileChangePermsCmd: the platform-dependent command to change file permissions to user-only read-write permissions.- The rest of the parameter/value pairs may retain the given default values.
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.
Generating verbose log output is a critical aid in troubleshooting of the DRS and is useful
when communicating problems to Globus support lists. To increase logging detail, add the following
line to the $GLOBUS_LOCATION/container-log4j.properties file.
... log4j.category.org.globus.replica=DEBUG ...