Next: Testing the Installation
Up: EDG Replica Manager Deployment
Previous: LCFGng configuration
Configuration File edg-replica-manager.conf
As mentioned before, the default configuration file will be
in the following location:
$EDG_LOCATION/var/etc/edg-replica-manager/edg-replica-manager.conf
The parameters are:
- location: You can either give your default CE or default
SE. This parameter is used to bootstrap the info services and to
know where the client tool is located. These options have to be
set in all cases and need to be configured in the post-install
step described above (manual or lcfg).
- file copy method: The URL copy functionality is
implemented in pure Java, using CoG as well as through JNI using the
(native) GASS copy C library. If you don't have the globus native
libraries installed, you still can use the package by switching to
the CoG-based implementation. However, it comes with a performance
hit: the CoG implementation does not allow for multiple parallel
streams for file transfers and is generally slower. The two possible
values are as follows:
org.edg.data.reptor.storage.GlobusURLCopyCoGImpl
org.edg.data.reptor.storage.GlobusURLCopyNativeImpl
- GridFTP service utilities like exists,
file size, mkdir etc. are implemented either
through CoG in pure Java or through JNI using the GridFTP C client
library. Similarly as for the file copy method, the two
implementations that you may use are:
org.edg.data.reptor.storage.GridFTPCoGImpl
org.edg.data.reptor.storage.GridFTPNativeImpl
- Information service: This is the main parameter to
configure an information service that is then used for all for
information service requests. In addition, information about
services like RLS, RMC and ROS is obtained from the information
service.
EDG Replica Manager can be used with R-GMA, MDS or it can read all
information from a configuration file. The following implementations are
available:
org.edg.data.reptor.info.InfoServiceStub
org.edg.data.reptor.info.InfoServiceRGMA
org.edg.data.reptor.info.InfoServiceMDS
- Stub:
The Stub does not read any
information from an information service but from a configuration
file specified by another property, config.infoservice
- RGMA: If this class is used, R-GMA is
contacted for all information service requests.
- MDS: If this class is used, MDS is
contacted for all information service requests.
- SRM specific properties can be set: retry interval,
timeouts etc. Please refer to Appendix A for details.
- failIfNoROS if this is set to false, then the replica
manager will not fail if no ROS is available. By default it is
set to true. Of course the optimization commands will become meaningless
in this case and will exit with an error.
Next: Testing the Installation
Up: EDG Replica Manager Deployment
Previous: LCFGng configuration
2005-02-04