The site-info.def file

The `site-info.def` file
Prev	Section 1. Installing dCache	Next

The `site-info.def` file

The site-info.def file contains a description of your site and is used by the install process to configure dCache correctly.

Locating Java

As dCache uses Java, you will need to know the path to your installation of Java Development Kit (JDK). Please note this is not the path to the runtime environment (JRE), which is often a subdirectory within the JDK.

[root@dcache-node] # rpm -qa|grep jdk
jdk-1.5.0_16-fcs
[root@dcache-node] # rpm -ql jdk-1.5.0_16-fcs | grep bin/java$
/usr/java/jdk1.5.0_16/bin/java
/usr/java/jdk1.5.0_16/jre/bin/java

In the above example, the JDK path is /usr/java/jdk1.5.0_16.

You must update your /root/site-info.def file, altering the values of the following variables: MY_DOMAIN, JAVA_LOCATION, USERS_CONF, DCACHE_ADMIN, DCACHE_POOLS, DCACHE_DOOR_SRM, DCACHE_DOOR_GSIFTP, DCACHE_DOOR_XROOTD, DCACHE_DOOR_LDAP and VOS. Suitable values are given below.

MY_DOMAIN=fzk.de
USERS_CONF=/root/users.conf

How to establish JAVA_LOCATION is described above
JAVA_LOCATION="/usr/java/jdk1.5.0_16"

Remember to replace dcache-node.fzk.de with the FQDN of this host
DCACHE_ADMIN="dcache-node.fzk.de"
DCACHE_POOLS="dcache-node.fzk.de:7:/pools/1   \
              dcache-node.fzk.de:7:/pools/2"

DCACHE_DOOR_SRM="dcache-node.fzk.de"
DCACHE_DOOR_GSIFTP="dcache-node.fzk.de"
DCACHE_DOOR_GSIDCAP="dcache-node.fzk.de"
DCACHE_DOOR_DCAP="dcache-node.fzk.de"
DCACHE_DOOR_XROOTD="dcache-node.fzk.de"
DCACHE_DOOR_LDAP="dcache-node.fzk.de"

VOS="dteam gks"

Note

Please be aware that there are two DCACHE_DOOR_XROOTD variables declared in the site-info.def file. This will be fixed with the next release, but in the mean-time, simply delete the extra instance.

You will need to add some extra configuration for the gks VO. The default site-info.def file contains information about common VOs, but this does not include the gks VO. Because of this, the following information should be appended to the site-info.def file.

# ======== GKS ======
VO_GKS_SW_DIR=...
VO_GKS_DEFAULT_SE=...
VO_GKS_STORAGE_DIR=...
VO_GKS_VOMS_SERVERS="vomss://dgrid-voms.fzk.de:8443/voms/gks?/gks/"
VO_GKS_VOMSES="gks dgrid-voms.fzk.de 15025 /O=GermanGrid/OU=FZK/CN=host/dgrid-voms.fzk.de gks"
VO_GKS_VOMS_CA_DN="'/C=DE/O=GermanGrid/CN=GridKa-CA'"

When running dCacheConfigure.sh, you must explicitly allow the script to reset various configuration options. This means you must either uncomment the existing lines or add extra lines.

RESET_DCACHE_CONFIGURATION=yes
RESET_DCACHE_PNFS=yes
RESET_DCACHE_RDBMS=yes

With these lines in place, you must run dCacheConfigure.sh to configure dCache. Be patient, it may take several minutes to run.

[root@dcache-node] # /opt/d-cache/bin/dCacheConfigure.sh -c config_sedcache -s /root/site-info.def
   WARNING: file /etc/init.d/pnfs does not exist
Stopping postgresql service:                               [FAILED]
Initializing database:
/var/lib/pgsql/data is missing. Use "service postgresql initdb" to initialize the cluster first.
                                                           [FAILED]
/var/lib/pgsql
Initializing database:                                     [  OK  ]
Stopping postgresql service:                               [FAILED]
Starting postgresql service:                               [  OK  ]
Starting postgresql service:                               [  OK  ]
Starting postgresql service:                               [  OK  ]
(there are many other lines of output)
D-cache takes some time to initialise. Please wait 8-10 Min's for the service to start.

Warning

After running dCacheConfigure.sh you should remove or comment-out the three lines that start RESET_. Failure to do this will reset vital data when you next run dCacheConfigure.sh, almost certainly resulting in data loss.

Prev	Up	Next
The `users.conf` file	Home	Starting and stopping dCache