Before Starting

• SL5 / 64bit installation according to the generic guidelines
• host certificate required

Service installation

• Setup repositories

# wget http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm
# rpm -ivh epel-release-5-4.noarch.rpm

# wget http://emisoft.web.cern.ch/emisoft/dist/EMI/1/sl5/x86_64/base/emi-release-1.0.0-1.sl5.noarch.rpm
# rpm -ivh emi-release-1.0.0-1.sl5.noarch.rpm
# wget http://emisoft.web.cern.ch/emisoft/dist/EMI/deployment/1/repos/emi-1-updates.repo -O /etc/yum.repos.d/emi-1-updates.repo

• Install middleware
  • because of problems with dependencies on Oracle RPMS you should use Oracle RPMs from cernonly repository (for more details read notes in the GGUS ticket or release notes )

# yum install emi-fts_oracle emi-fta_oracle

• Install Certificates

# yum install lcg-CA

# wget https://grid-deployment.web.cern.ch/grid-deployment/emi/repo/common/emi-tb-internal.repo -O /etc/yum.repos.d/emi-tb-internal.repo
# yum install emi-tb-vomscerts

• Additionally for succesful YAIM configuration 2 packages have to be installed manually (no dependencies on them - should be added maybe?): xml-commons-apis, oracle-instantclient-sqlplus. Lack of xml-xommon-apis causes the error below, but seems to be harmless for the services.

/usr/bin/rebuild-jar-repository: error: Could not find xml-commons-apis Java extension for this JVM
/usr/bin/rebuild-jar-repository: error: Some detected jars were not found for this jvm
Starting tomcat5:                                          [  OK  ]

Service Configuration

# /opt/glite/yaim/bin/yaim -c -s site-info.def -n emi_fts2 -n emi_fta2

with following site-info.def skeleton:

SITE_NAME=cert-tb-cern

USERS_CONF=/root/yaim/users.conf
GROUPS_CONF=/root/yaim/groups.conf

BDII_HOST=certtb-bdii.cern.ch
PX_HOST=emitb2.ics.muni.cz

###################################
# FTS configuration variables #
###################################

FTS_HOST=`hostname -f`
FTS_HOST_ALIAS=$FTS_HOST

ORACLE_LOCATION=/usr/lib64/oracle/10.2.0.4

FTS_SERVER_URL="https://${FTS_HOST_ALIAS}:8443/glite-data-transfer-fts"
FTS_DBURL="jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=...)(PORT=...))(ADDRESS=(PROTOCOL=TCP)(HOST=...)(PORT=...))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=...)))"
FTS_DB_TYPE=ORACLE

FTS_DB_USER=oracle_db_user
FTS_DB_PASSWORD=oracle_db_user_password


####################################
#FTA configuration variables              #
###################################
FTA_MACHINES="ONE"

FTA_AGENTS_ONE_HOSTNAME=$FTS_HOST
FTA_AGENTS_ONE="DTEAM CERNCERN CERNDESY TESTERSEMI"

FTA_CERNCERN=URLCOPY
FTA_CERNDESY=URLCOPY
FTA_DTEAM="VOAGENT"
FTA_TESTERSEMI="VOAGENT"

FTA_GLOBAL_DBTYPE=ORACLE
FTA_GLOBAL_DB_CONNECTSTRING="(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=...)(PORT=...))(ADDRESS=(PROTOCOL=TCP)(HOST=...)(PORT=...))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=....)))"
FTA_GLOBAL_DB_USER=oracle_db_user
FTA_GLOBAL_DB_PASSWORD=oracle_db_user_password

##############################
# VO configuration variables #
##############################
[...]

Note that:

• YAIM may ask several times for executing commands for creating proper schema in oracle database (especially if the service is being configured for the 1st time with the DB instance).
• each channel defined in site-info have to be manually added by service admin (otherwise transfer agents for channels cannot be started), example for one channel:

# glite-transfer-channel-add -s https://cvitbrc04.cern.ch:8443/glite-data-transfer-fts/services/ChannelManagement CERNDESY cert-tb-cern desycerttb

# LCG_GFAL_INFOSYS=cvitbbdii1.cern.ch:2170 glite-transfer-channel-add  -s https://cvitbrc04.cern.ch:8443/glite-data-transfer-fts/services/ChannelManagement TESTERSEMI

• relation between channel and VO in done by defining a VO share:

# LCG_GFAL_INFOSYS=cvitbbdii1.cern.ch:2170 /usr/bin/glite-transfer-channel-setvoshare  -s https://cvitbrc04.cern.ch:8443/glite-data-transfer-fts/services/ChannelManagement TESTERSEMI testers.eu-emi.eu 50

• channel information in database:

# sqlplus db_username/db_password@"(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=...)(PORT=...))(ADDRESS=(PROTOCOL=TCP)(HOST=...)(PORT=...))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=...)))"

SQL> select channel_name from t_channel;
SQL> select * from tab;
SQL> select * from t_channel_vo_share;

Service Testing

Basic test:

• check running daemons (see links and service reference card for details)

• after getting proxy on UI:

$ glite-transfer-channel-list -s https://cvitbrc04.cern.ch:8443/glite-data-transfer-fts/services/ChannelManagement
# Using endpoint https://cvitbrc04.cern.ch:8443/glite-data-transfer-fts/services/ChannelManagement
# Service version: 3.7.6-1
# Interface version: 3.7.0
# Schema version: 3.5.0
# Service features: glite-data-fts-service-3.7.6-1
# Client version: 3.7.3
# Client interface version: 3.7.0
CERNCERN
CERNDESY

$ glite-transfer-channel-list -s https://cvitbrc04.cern.ch:8443/glite-data-transfer-fts/services/ChannelManagement  -v CERNCERN

# Using endpoint https://cvitbrc04.cern.ch:8443/glite-data-transfer-fts/services/ChannelManagement
# Service version: 3.7.6-1
# Interface version: 3.7.0
# Schema version: 3.5.0
# Service features: glite-data-fts-service-3.7.6-1
# Client version: 3.7.3
# Client interface version: 3.7.0
Channel: CERNCERN
Between: CERT-TB-CERN and CERT-TB-CERN
State: Active
Contact: (null)
Bandwidth: 0
Nominal throughput: 0
Number of files: 0, streams: 0
Number of VO shares: 0


$ glite-transfer-submit -v -o -s https://cvitbrc04.cern.ch:8443/glite-data-transfer-fts/services/FileTransfer  srm://lxbra2502.cern.ch:8446/dpm/cern.ch/home/dteam/testfile1 srm://cvitbdpm1.cern.ch:8446/dpm/cern.ch/home/dteam/testfile3

# Using endpoint https://cvitbrc04.cern.ch:8443/glite-data-transfer-fts/services/FileTransfer
# Service version: 3.7.6-1
# Interface version: 3.7.0
# Schema version: 3.5.0
# Service features: glite-data-fts-service-3.7.6-1
# Client version: 3.7.3
# Client interface version: 3.7.0
Server supports delegation. Delegation will be used by default.
Remaining time for local proxy is 5 hours and 6 minutes.
Will redo delegation since the credential on the server has left that 4 hours validity left.
Remaining time for this credential is 5 hours and 4 minutes.
Requesting delegated proxy for 5 hours and 5 minutes.
Credential is succesfully delegated to the service.
610ab12d-d577-11e0-978a-cf1c28e08497

$ glite-transfer-status -v -s https://cvitbrc04.cern.ch:8443/glite-data-transfer-fts/services/FileTransfer 610ab12d-d577-11e0-978a-cf1c28e08497

Links

• EMI FTS
• gLite FTS
  • FTS Admin Guide
  • Reference card

• FTS 2.2.6 Release notes
• FTS Configuration
• FTS YAIM reference
• FTS installation
• FTS Channel Creation(GILDA - broken?)
• FTS Channel Creation (EUMEDGRID)
• FTS Usage
• FTS WLCG

-- TomaszWolak - 01-Sep-2011