DataGRID. Lead Partner: Document status:

Transcription

1 DataGRID EDG REPLICATION METADATA USER GUIDE TESTBED 2.0 Document identifier: EDMS id: Work package: Partner(s): Lead Partner: Document status: Author(s): File: WP02: Data Management CERN, PPARC, HIP, INFN, ITC, KDC CERN FINAL Leanne Guy, Sophie Lemaitre edg-rmc-userguide Abstract: This is the user guide for the EDG Replication Metadata Catalogue developed by WP2. The Replication Metadata Catalogue is a system that maintains information about the mappings between the Grid Unique Identifiers (GUIDs) and Logical File Name (LFN) aliases, as well as holding LFN metadata and possibly some application level metadata. IST INTERNAL 1/19

2 CONTENTS 1. INTRODUCTION OBJECTIVES OF THIS DOCUMENT APPLICATION AREA APPLICABLE DOCUMENTS AND REFERENCE DOCUMENTS TERMINOLOGY THE EDG REPLICATION METADATA CATALOGUE 6 3. EDG REPLICATION METADATA CATALOGUE REQUIREMENTS 6 4. EDG REPLICATION METADATA CATALOGUE COMMAND LINE TOOLS COMMAND LINE TOOL USAGE AND HELP EDG-REPLICA-METADATA-CATALOG-ADMIN PING EDG-REPLICA-METADATA-CATALOG ADDALIAS ALIASEXISTS GUIDEXISTS GUIDFORALIAS ALIASESFORGUID REMOVEALIAS GETRESULTLENGTH SETRESULTLENGTH ADDGUIDATTRDEFN REMOVEGUIDATTRDEFN GUIDATTRDEFNEXISTS LISTGUIDATTRDEFNS ADDALIASATTRDEFN REMOVEALIASATTRDEFN ALIASATTRDEFNEXISTS LISTALIASATTRDEFNS MAPPINGSBYGUID MAPPINGSBYALIAS MAPPINGSBYGUIDATTR MAPPINGSBYALIASATTR SETGUIDATTR GETGUIDATTR REMOVEGUIDATTR SETALIASATTR IST INTERNAL 2/19

3 GETALIASATTR REMOVEALIASATTR GETVERSION MAXLENGTH COMMANDLINE TOOL LOGGING SUPPORT 19 IST INTERNAL 3/19

4 Document Change Record Issue Date Comment Author /02/2003 First Draft Leanne Guy /02/2003 CLI section Sophie Lemaitre /03/2003 Checked and updated CLI Leanne Guy /04/2003 Add logging documentation Peter Kunszt /06/2003 Update according to the CLI changes Sophie Lemaitre IST INTERNAL 4/19

5 1. INTRODUCTION 1.1. OBJECTIVES OF THIS DOCUMENT This document describes how to use the EDG Replica Location Service (EDG-RLS) command line interface APPLICATION AREA EDG-WP2 Data Management. This document is intended for users of the EDG Replication Metadata Catalogue, the aim being to describe the use of the command line interface APPLICABLE DOCUMENTS AND REFERENCE DOCUMENTS Applicable documents [A1] [A2] [A3] [A4] [A5] [A6] [A7] D2.2 WP2 Architecture and Design Document. D12.2 DataGrid Naming Conventions document, WP12 Project Management. D12.2 DataGrid Developers Guide, Quality Assurance Group. DataGrid-12-TED , D12.4 DataGrid Architecture DX.X EDG Replication Metadata Catalogue Installation Guide. DX.X EDG Replica Location Service Installation Guide. DX.X EDG Replica Location Service User Guide. Reference documents [R1] [R2] L. Guy, E. Laure, P. Kunszt, E. Laure, H. Stockinger, K. Stockinger, Replica Management in DataGrids. Presented at GGF5. Giggle: A Framework for Constructing Scalable Replica Location Services. In Proc. of the Int l. IEEE/ACM Supercomputing Conference (SC 2002), Baltimore, USA, November A. Chervenak, E.Deelman, I. Foster, L. Guy, A. Iamnitchi, C. Kesselman, W. Hoschek, M. Ripeanu, B. Schwartzkopf, H. Stockinger, K. Stockinger, and B. Tierney. Giggle: A Framework for Constructing Scalable Replica Location Services. In SC 2002, Baltimore, USA, November TERMINOLOGY Definitions API CLI EDG LCN LRC RLI RLS RMC SFN Application Programming Interface Command Line Interface European DataGrid Logical Collection Name Local Replica Catalogue Replica Location Index Replica Location Service Replication Metadata Catalogue Storage File Name IST INTERNAL 5/19

6 Glossary GUID Grid Unique IDentifier A UUID generated by the Replica Management System for an SFN. It is created at the SFN registration time. A GUID is immutable. UUID Universally Unique IDentifier A UUID is a 128 bits long number, and is either guaranteed to be different from all other UUIDs generated until 3400 A.D. or extremely likely to be different (depending on the mechanism chosen to generate it). LFN Logical File Name A Logical File Name is a user defined alias to a GUID. Unlike GUIDs, aliases are mutable but they still should be globally unique. Since the Replica Management System has no control over the creation of LFNs, this global uniqueness is only weakly enforced. LRC Local Replica Catalogue The LRC stores GUID to SFN mappings, along with SFN attributes for either a single site, or a single Storage Resource Manager at a single site. Only GUID to SFN mappings for those SFNs physically located at the same site are stored in the LRC. An LRC is indexed by an RLI. RLI Replica Location Index An RLI indexes over all LRCs that subscribe to it. The RLI stores GUID to LRC mappings, thus maintaining a catalogue of all LRCs that store at least one physical replica of a given GUID. This provides the link between different LRCs, allowing for distributed indexing and querying of all LRCs. RLS Replica Location Service The RLS is a system that maintains information about the physical locations of logical identifiers of data and provides access to this information. It consists of two internal components, a Local Replica Catalogue (LRC) and a Replica Location Index (RLI). It is the successor to the Replica Catalogue. RMC Replication Metadata Catalogue The EDG-RMC is a system that LFN aliases to GUID mappings, as well as attributes on GUIDs and LFNs. SFN Storage File Name An SFN is a locater for a physical file, where the scheme specific part is understood by a Storage Resource Manager (SRM). It is a URL where the scheme is sfn and the host is a valid SRM host. IST INTERNAL 6/19

7 2. THE EDG REPLICATION METADATA CATALOGUE The EDG Replication Metadata Catalogue stores mappings between user defined LFN aliases to GUIDs. The EDG-RMC is not forseen to provide a full metadata service for event and application specific metadata, only to facilitate the task of data replication and access. The EDG-RMC works together with the EDG-RLS LFN to SFN mappings are many to many mappings and the GUIDs provide for the unique identification of all data files. The EDG-RLS stores the mappings between GUIDS and all physical replicas of a given data file; that is GUID to SFN mappings, as well as any attributes or metadata on the physical files themselves. Applications and users are free to define aliases to GUIDs. These aliases are stored in the EDG-RMC along with information about Logical Collection Names (LCNs) as well as GUID metadata such as file size, owner, acls, which are required for successful data file replication. As for the EDG-RLS, the EDG-RMC has been tested to date with two different database backends, MySQL and Oracle. This is described in more detail in the installation guide [?]. 3. EDG REPLICATION METADATA CATALOGUE REQUIREMENTS If you have installed the EDG- Replication Metadata Catalogue client on a standalone node,i.e a desktop PC that does not have any EDG software installed on it, you must set the following environment variables, as described in the EDG Developers Guide [A3]. EDG LOCATION=/opt/edg EDG LOCATION VAR=/opt/edg/var EDG TMP=/tmp X509 USER CERT=/etc/grid-security/hostcert.pem X509 USER KEY=/etc/grid-security/hostkey.pem GRIDMAP=/etc/grid-security/grid-mapfile GRIDMAPDIR=/etc/grid-security/gridmapdir If these variables are different on your machine, set them accordingly. 4. EDG REPLICATION METADATA CATALOGUE COMMAND LINE TOOLS Two command line tools are provided for use of the EDG Replication Metadata Catalogue, for which both a long and short version exist: edg-replica-metadata-catalog-admin or edg-rmc-admin edg-replica-metadata-catalog or edg-rmc The first allows for administration of the EDG Replication Metadata Catalogue and the second allows use of the EDG Replication Metadata Catalogue. In all cases, to connect to a server that hosts an EDG Replication Metadata Catalogue you must specify an EDG-RMC server name using the -h or host option: IST INTERNAL 7/19

8 If the connection is insecure (i.e. if you want to use http or a hostname), with insecure. It is secure by default, i.e. it uses https by default. The hostname of the server to connect to : for instance -h localhost. The port, if it is not the port by default (8080), with the -p option. The path, if it is not the path by default (edg-metadata-catalog/services/edg-metadata-catalog), with the option COMMAND LINE TOOL USAGE AND HELP To get all the administration commands, just type : $EDG LOCATION/bin/edg-replica-metadata-catalog-admin -h usage: edg-replica-metadata-catalog-admin [options] command [options] -h,--help print help (if command is given, details on command) -i,--insecure Connect in an insecure manner, i.e. not https. -v,--verbose print additional information while executing Commands: Administration commands ping Check if the server is alive. A full list of all commands and options for the EDG-RMC is available with $EDG LOCATION/bin/edg-replica-metadata-catalog -h usage: edg-replica-metadata-catalog [options] command [options] -h,--help print help (if command is given, details on command) -i,--insecure Connect in an insecure manner, i.e. not https. -v,--verbose print additional information while executing Commands: Attribute commands addalias aliasexists guidexists guidforalias aliasesforguid removealias getresultlength setresultlength Add a new alias to GUID mapping Does the alias exist in this catalog? Does the GUID exist in this catalog? Return the GUID for a given Alias. Return the aliases for a given GUID. Remove an alias from a given GUID. Return the result length by default (i.e. how many mappings will be returned when using mappingsbyguid or mappingsbypfn). Set the result length by default (i.e. how many mappings will be returned when using mappingsbyguid or mappingsbypfn). Guid Attribute management commands IST INTERNAL 8/19

9 addguidattrdefn removeguidattrdefn guidattrdefnexists listguidattrdefns Add a new guid attribute definition to the catalog. Remove an guid attribute definition from the catalog. Is a given guid attribute definition in the catalog. List the guid attribute definitions in the catalog. Alias Attribute management commands addaliasattrdefn removealiasattrdefn aliasattrdefnexists listaliasattrdefns Add a new alias attribute definition to the catalog. Remove an alias attribute definition from the catalog. Is a given alias attribute definition in the catalog. List the alias attribute definitions in the catalog. Wildcard query commands mappingsbyguid mappingsbyalias mappingsbyguidattr mappingsbyaliasattr Get a set of mappings by a wildcard search on guid. Get a set of mappings by a wildcard search on alias name. Get a set of mappings by a wildcard search on guid attribute value. Get a set of mappings by a wildcard search on alias attribute value. GUID attribute commands setguidattr getguidattr removeguidattr Set an guid attribute. Get an guid attribute. Remove an guid attribute. Alias attribute commands setaliasattr getaliasattr removealiasattr Set an alias attribute. Get an alias attribute. Remove an alias attribute. Other commands getversion maxlength Get the client and server versions. Return the maximum length (i.e. the maximum number of characters) for a GUID, an Alias or an Attribute name. IST INTERNAL 9/19

10 4.2. EDG-REPLICA-METADATA-CATALOG-ADMIN The edg-replica-metadata-catalog-admin command line tool provides administration options for the EDG Replication Metadata Catalogue. edg-replica-metadata-catalog-admin -h, help print help -i, insecure.connect in an insecure manner, i.e. not https. -v, verbose print in verbose mode Commands: Examples: $EDG LOCATION/bin/edg-replica-metadata-catalog-admin -h $EDG LOCATION/bin/edg-rmc help PING The ping command pings an EDG Replication Metadata Catalogue server. The status report will return the number of GUIDs and LFN aliases in the catalogue. Return Values: ping hostname The name of the server to ping. $EDG LOCATION/bin/edg-replica-metadata-catalog-admin insecure ping -h localhost OK : 0 GUIDs, 0 aliases EDG-REPLICA-METADATA-CATALOG The edg-replica-metadata-catalog command line tool exists in both long and short form; edg-rmc and edg-replica-metadata-catalog. edg-replica-metadata-catalog -h, help print help -i, insecure.connect in an insecure manner, i.e. not https. -v, verbose print in verbose mode Commands: Examples: $EDG LOCATION/bin/edg-replica-metadata-catalog -h $EDG LOCATION/bin/edg-rmc help ADDALIAS The addalias command creates a new user defined alias to a GUID in the EDG-RMC. If the specified GUID does not exist already it is created in the EDG-RMC. If it exists already, then a new mapping between the LFN and existing alias. If the GUID-Alias mapping exists already an error message will be returned, otherwise no notification is given. IST INTERNAL 10/19

11 addalias The arguments must be supplied in this order guid: the GUID. alias: the corresponding alias. Examples: $EDG LOCATION/bin/edg-replica-metadata-catalog insecure addalias guid:guid1 alias:alias1 -h localhost $EDG LOCATION/bin/edg-rmc -i addalias guid:guid1 alias:alias1 -h localhost -p 8080 Return Values: Alias already exists : alias:alias ALIASEXISTS The aliasexists command checks for the existence of a given alias in the EDG-RMC. It does not return any GUID-Alias mappings, it only checks for the existence of a given alias, returning a boolean. aliasexists alias the alias to query for in the Catalog. $EDG LOCATION/bin/edg-replica-metadata-catalog insecure aliasexists alias:alias1 -h localhost Return Values: Alias exists : alias:alias1 Alias does not exist : alias:alias GUIDEXISTS The guidexists command checks for the existence of a given GUID in the EDG-RMC. It does not return any GUID-Alias mappings, it only checks for the existence of a given GUID, returning a boolean. guidexists guid the GUID to query for in the Catalog. $EDG LOCATION/bin/edg-replica-metadata-catalog insecure guidexists guid:guid1 -h localhost Return Values: GUID exists : guid:guid1 GUID does not exist : guid:guid GUIDFORALIAS The guidforalias command returns the GUID for a given alias. Aliases cannot point to more than one GUID so only one GUID will be returned if the alias exists, otherwise and error message will be returned. IST INTERNAL 11/19

12 Return Values: guidforalias alias the alias to get the GUID for. $EDG LOCATION/bin/edg-rmc insecure guidforalias alias:alias1 -h localhost guid:guid1 No such alias : alias:alias ALIASESFORGUID The aliasesforguid command returns a comma delimited list of all aliases that exist for a given GUID. aliasesforguid guid the GUID to get the aliases for. $EDG LOCATION/bin/edg-replica-metadata-catalog insecure aliasesforguid guid:guid1 -h localhost Return Values: alias:alias1, alias:alias2, alias:alias3, alias:alias4 No such guid : guid:guid REMOVEALIAS The removealias command will remove a single given GUID-Alias mapping from the EDG-RMC. Multiple alias removal is not supported. Regardless of whether the alias does not exist, or the PFN exists and is successfully removed, no output message is given. removealias guid the GUID to remove the alias from. alias the alias to remove to the Catalog. $EDG LOCATION/bin/edg-replica-metadata-catalog insecure removealias guid:guid1 alias:alias1 -h localhost GETRESULTLENGTH The getresultlength command will return the result length by default for the mappingsbyguid and mappingsbyalias commands. If the default result length is set to 20, only the 20 first mappings will be displayed when using mappingsbyguid or mappingsbyalias. You can change the default result length by using the setresultlength command (see below). IST INTERNAL 12/19

13 getresultlength none. path path on the server to connect to Examples: $EDG LOCATION/bin/edg-replica-metadata-catalog insecure getresultlength -h localhost Return: SETRESULTLENGTH The getresultlength command will set the result length by default for the mappingsbyguid and mappingsbyalias commands. If the default result length is set to 20, only the 20 first mappings will be displayed when using mappingsbyguid or mappingsbyalias. setresultlength resultlength the result length by default. path path on the server to connect to Examples: $EDG LOCATION/bin/edg-replica-metadata-catalog insecure setresultlength h localhost ADDGUIDATTRDEFN The addguidattrdefn command will create a new GUID attribute definition in the EDG-RMC, for example the size of the file may be defined as a GUID attribute. If the attribute definition exists already an error is returned, otherwise nothing is returned. Return Values: addguidattrdefn defnname the name of the GUID attribute to add. defntype the type of the GUID attribute to add. $EDG LOCATION/bin/edg-replica-metadata-catalog insecure addguidattrdefn Creator string -h localhost Attribute definition exists : Creator REMOVEGUIDATTRDEFN The removeguidattrdefn command will remove a GUID attribute definition from the EDG-RMC. Regardless of whether the attribute definition does not exist, or the attribute definition exists and is successfully removed, no output message is given. IST INTERNAL 13/19

14 removeguidattrdefn defnname the GUID attribute name to remove. $EDG LOCATION/bin/edg-replica-metadata-catalog insecure removeguidattrdefn Creator -h localhost GUIDATTRDEFNEXISTS The guidattrdefnexists command informs whether a GUID attribute definition exists in the EDG-RMC. Description: Return Values: guidattrdefnexists Informs if a given GUID attribute definition exists in the Catalog. defnname the GUID attribute definition to check for in the Catalog. $EDG LOCATION/bin/edg-replica-metadata-catalog insecure guidattrdefnexists Creator -h localhost Attribute definition exists : Creator Attribute definition does not exist : Creator LISTGUIDATTRDEFNS The listguidattrdefns returns a list of all the attribute names and types that are defined in the EDG-RMC. Return Values: listguidattrdefns $EDG LOCATION/bin/edg-replica-metadata-catalog insecure listguidattrdefns -h localhost Creator, string ADDALIASATTRDEFN The addaliasattrdefn command will create a new Alias attribute definition in the EDG-RMC, for example the size of the file may be defined as a Alias attribute. If the attribute definition exists already an error is returned, otherwise nothing is returned. Return Values: addaliasattrdefn defnname the name of the Alias attribute to add. defntype the type of the Alias attribute to add. $EDG LOCATION/bin/edg-replica-metadata-catalog insecure addaliasattrdefn Creator string -h localhost Attribute definition exists : Creator IST INTERNAL 14/19

15 REMOVEALIASATTRDEFN The removealiasattrdefn command will remove a Alias attribute definition from the EDG-RMC. Regardless of whether the attribute definition does not exist, or the attribute definition exists and is successfully removed, no output message is given. removealiasattrdefn defnname the Alias attribute name to remove. $EDG LOCATION/bin/edg-replica-metadata-catalog insecure removealiasattrdefn Creator -h localhost ALIASATTRDEFNEXISTS The aliasattrdefnexists command informs whether a Alias attribute definition exists in the EDG-RMC. Description: Return Values: aliasattrdefnexists Informs if a given Alias attribute definition exists in the Catalog. defnname the Alias attribute definition to check for in the Catalog. $EDG LOCATION/bin/edg-replica-metadata-catalog insecure aliasattrdefnexists Creator -h localhost Attribute definition exists : Creator Attribute definition does not exist : Creator LISTALIASATTRDEFNS The listaliasattrdefns returns a list of all the attribute names and types that are defined in the EDG- RMC. Return Values: listaliasattrdefns $EDG LOCATION/bin/edg-replica-metadata-catalog insecure listaliasattrdefns -h localhost Creator, string MAPPINGSBYGUID The mappingsbyguid command returns a list of all mappings for a given GUID wildcard pattern, or an exact GUID name. IST INTERNAL 15/19

16 mappingsbyguid guidpattern the GUId pattern to get the mappings for. : $EDG LOCATION/bin/edg-replica-metadata-catalog insecure mappingsbyguid guid:guid1 -h localhost $EDG LOCATION/bin/edg-replica-metadata-catalog insecure mappingsbyguid * -h localhost $EDG LOCATION/bin/edg-replica-metadata-catalog insecure mappingsbyguid *guid -h localhost Return Values: guid:guid1, alias:alias1 guid:guid1, alias:alias2 guid:guid1, alias:alias MAPPINGSBYALIAS The mappingsbyalias command returns a list of all mappings in the EDG-RMC for a given alias wildcard pattern, or an exact alias. Return Values: mappingsbyalias aliaspattern the alias pattern to get the mappings for. $EDG LOCATION/bin/edg-replica-metadata-catalog insecure mappingsbyalias alias:alias1 -h localhost $EDG LOCATION/bin/edg-replica-metadata-catalog insecure mappingsbyalias * -h localhost guid:guid1, alias:alias1 guid:guid1, alias:alias2 guid:guid1, alias:alias MAPPINGSBYGUIDATTR The mappingsbyguidattr command returns a list of all mappings for a given GUID attribute name wildcard pattern, or an exact GUID attribute name. Return Values: mappingsbyguidattr guidattrpattern the GUID attribute name pattern to get the mappings for. $EDG LOCATION/bin/edg-replica-metadata-catalog insecure mappingsbyguidattr Creator -h localhost $EDG LOCATION/bin/edg-replica-metadata-catalog insecure mappingsbyguidattr Crea* -h localhost $EDG LOCATION/bin/edg-replica-metadata-catalog insecure mappingsbyguidattr *tor -h localhost guid:guid1, alias:alias1 guid:guid1, alias:alias2 guid:guid1, alias:alias3 IST INTERNAL 16/19

17 MAPPINGSBYALIASATTR The mappingsbyaliasattr command returns a list of all mappings for a given Alias attribute name wildcard pattern, or an exact Alias attribute name. mappingsbyaliasattr aliasattrpattern the Alias attribute name pattern to get the mappings for. $EDG LOCATION/bin/edg-replica-metadata-catalog insecure mappings- ByAliasAttr Creator -h localhost $EDG LOCATION/bin/edg-replica-metadata-catalog insecure mappings- ByAliasAttr Crea* -h localhost $EDG LOCATION/bin/edg-replica-metadata-catalog insecure mappings- ByAliasAttr *tor -h localhost Return Values: guid:guid1, alias:alias1 guid:guid1, alias:alias2 guid:guid1, alias:alias SETGUIDATTR The setguidattr command assigns a value for an attribute to a given GUID. An error is returned if the attibute definition does not exist. If the attribute value is successfully assigned, no message is returned. setguidattr guid the name of the GUID. guidattrname the name of the GUID attribute. value the value of the attribute. $EDG LOCATION/bin/edg-replica-metadata-catalog insecure setguidattr guid:guid1 Creator leanne -h localhost Return Values: No such attribute definition : FileName GETGUIDATTR The getguidattr returns the value of an attribute for a given GUID. An error is returned if the attibute definition does not exist. If the attribute definition exists but no value has been set for this GUID, nothing is returned. getguidattr guid the GUID. guidattrname the name of the GUID attibute. $EDG LOCATION/bin/edg-replica-metadata-catalog insecure getguidattr guid:guid1 Creator -h localhost Return Values: leanne No such attribute definition : FileSe IST INTERNAL 17/19

18 REMOVEGUIDATTR The removeguidattr command will remove the value of an GUID attribute for a given GUID. The GUID attribute definition is not removed from the EDG-RMC. removeguidattr guid the name of the GUID. guidattrname the name of the GUID attribute. $EDG LOCATION/bin/edg-replica-metadata-catalog -i removeguidattr guid:guid1 Creator -h localhost Return Values: NO ERROR SETALIASATTR The setaliasattr command assigns a value for an attribute to a given Alias. An error is returned if the attibute definition does not exist. If the attribute value is successfully assigned, no message is returned. setaliasattr alias the name of the Alias. aliasattrname the name of the Alias attribute. value the value of the attribute. $EDG LOCATION/bin/edg-replica-metadata-catalog insecure setaliasattr alias:alias1 Creator leanne -h localhost Return Values: No such attribute definition : FileName GETALIASATTR The getaliasattr returns the value of an attribute for a given Alias. An error is returned if the attibute definition does not exist. If the attribute definition exists but no value has been set for this alias, nothing is returned. getaliasattr alias the alias. aliasattrname the name of the Alias attibute. $EDG LOCATION/bin/edg-replica-metadata-catalog insecure getaliasattr alias:alias1 Creator -h localhost Return Values: leanne No such attribute definition : FileSe REMOVEALIASATTR The removealiasattr command will remove the value of an Alias attribute for a given alias. The Alias attribute definition is not removed from the EDG-RMC. IST INTERNAL 18/19

19 removealiasattr alias the name of the alias. aliasattrname the name of the Alias attribute. $EDG LOCATION/bin/edg-replica-metadata-catalog -i removealiasattr alias:alias1 Creator -h localhost Return Values: NO ERROR GETVERSION Get the versions of the server and the client. getversion none. $EDG LOCATION/bin/edg-replica-metadata-catalog insecure getversion -h localhost Return Values: MAXLENGTH Get the maximum number of characters for a GUID, a PFN or an Attribute maxlength none. $EDG LOCATION/bin/edg-replica-metadata-catalog -i maxlength -h localhost Return Values: Maximum Length for a GUID : 250 Maximum Length for an Alias : 250 Maximum Length for an Attribute : COMMANDLINE TOOL LOGGING The command line tool will log its progress into a logfile usually placed under $EDG_TMP/edg-replica-metadata-catalog-<user>.log where the user is the actual user name that the user uses to run this command. If EDG TMP is not set, /tmp is used. To change the placement of the log file, set the variable EDG_REPLICA_METADATA_CATALOG_LOGFILE to the name of the log file. The full logging behavior is read from the log4j configuration file at $EDG_LOCATION/etc/edg-replica-metadata-catalog/log4j-client.properties IST INTERNAL 19/19

20 To read it from another file, specify it using the environment variable EDG_REPLICA_METADATA_CATALOG_LOGPROPERTIES The actual log file might be set through this file as well. The content of the default log file is # # A log4j logger configuration for the edg-replica-manager client # log4j.rootlogger=info, FILE log4j.appender.file=org.apache.log4j.fileappender log4j.appender.file.file=${log4j.log.location} log4j.appender.file.layout=org.apache.log4j.patternlayout # Print the date in ISO 8601 format log4j.appender.file.layout.conversionpattern=%d{iso8601} %-5p [%t] %c{2} %x - %m%n # # now control the level of logging we get output to the file # # Print only messages of level INFO or above in the package org.edg.data. log4j.logger.org.edg.data=info # Now shut down the level of logging we get from Axis on all loggers log4j.logger.org.apache.axis=warn log4j.logger.org.apache.axis.transport.http.axisservlet=fatal To raise the log level, change the line with log4j.logger.org.edg.data to the desired log level. If you set the file explicitly in log4j.appender.file.file then the environment variable for the log file will have no effect. For more information we refer the user to the log4j documentation. 5. SUPPORT Please direct all questions about the use of the EDG RMC to: WP2 replication <hep-proj-grid-data-mgtreplication@cern.ch> IST INTERNAL 20/19