release notes | Book: 1.9.5, 1.9.12 (opt, FHS), 2.11 (FHS), 2.12 (FHS), 2.13 (FHS), 2.14 (FHS), | Wiki | Q&A black_bg
Web: Multi-page, Single page | PDF: A4-size, Letter-size | eBook: epub black_bg

Configuring SRM Domain

Once database and and JVM are installed and database is running, you may install dCache SRM.

[return to top]

Install dCache server.rpm

[root] # rpm -Uvh <dcache.server.rpm>

[return to top]

node_config

Copy /pt/d-cache/etc/node_config.template into /opt/d-cache/etc/node_config

Edit /opt/d-cache/etc/node_config

NODE_TYPE=custom
...
SRM=yes
...
# all other parameters should be turned off on "srm only" node

[return to top]

srm_setup.env

Edit /opt/d-cache/etc/srm_setup.env

  • Make sure that JAVA_HOME is set to correct value, for example

    JAVA_HOME=/usr/java/jdk1.5.0_07

  • Tomcat port does not interfere with with services that are already using network

    TOMCAT_PORT=8080
  • If you are going to run the monitoring on the same node:

    TOMCAT_HTTP_ENABLED=true
    JAVA_OPTS="-Xmx512m -Djava.awt.headless=true"

[return to top]

install dCacheSetup

Copy /opt/d-cache/etc/dCacheSetup.template into /opt/d-cache/config/dCacheSetup and edit it so that, serviceLocatorHost and serviceLocatorPort point to central dcache node:

serviceLocatorHost=<host of central node>
serviceLocatorPort=<11111>

following SRM parameters should be configured as following:

srmVacuum=false
srmDbName=dcache
srmDbUser=srmdcache

Make sure that both srmCopyReqThreadPoolSize and remoteGsiftpMaxTransfers are set to the same values and the common value should be the roughly equal to the maximum number of the SRM - to -SRM copies your system can sustain. So if you think about 3 gridftp transfer per pool and you have 30 pools than the number should be 3x30=90.

srmCopyReqThreadPoolSize=90
remoteGsiftpMaxTransfers=90

Note US-CMS T1 has:

srmCopyReqThreadPoolSize=2000
remoteGsiftpMaxTransfers=2000

[return to top]

Tomcat/axis deployment

Run

[root] # /opt/d-cache/install/install.sh

[return to top]

Starting and stopping SRM domain

Run

[root] # /opt/d-cache/bin/dcache-core start

to start SRM domain.

Run

[root] # /opt/d-cache/bin/dcache-core stop

to stop SRM domain.

[return to top]

SRM Logs

SRM might produce a lot of logs, especially if it run in debug mode. Need to run SRM in debug mode is greatly reduced if SRM monitoring is installed. It is recommended to make sure that logs are redirected into a file on large disk. dCache SRM 1.7 logs into /opt/d-cache/libexec/apache-tomcat-5.5.20/logs/catalina.out.