Edit $PRODAGENT_WORKDIR/CreatorPluginConfig.xml to configure the stage out %CODE{"html"}% %ENDCODE% and software setup %CODE{"html"}% %ENDCODE% Start to configure the mysql database

prodAgent-edit-config --component=ProdAgentDB --parameter=user --value=root
prodAgent-edit-config --component=ProdAgentDB --parameter=passwd --value=YourProdAgentPassHere
prodAgent-edit-config --component=ProdAgentDB --parameter=socketFileLocation --value=$PRODAGENT_WORKDIR/mysqldata/mysql.sock
prodAgent-edit-config --component=ProdAgentDB --parameter=dbName --value=ProdAgentDB

mkdir $PRODAGENT_WORKDIR/mysqldata
mysql_install_db --datadir=$PRODAGENT_WORKDIR/mysqldata
mysqld_safe --datadir=$PRODAGENT_WORKDIR/mysqldata --socket=$PRODAGENT_WORKDIR/mysqldata/mysql.sock --skip-networking   --log-error=$PRODAGENT_WORKDIR/mysqldata/error.log --pid-file=$PRODAGENT_WORKDIR/mysqldata/mysqld.pid &
mysqladmin -u root password 'XXXXXXX' --socket=$PRODAGENT_WORKDIR/mysqldata/mysql.sock

prodAgent-install-db
prodAgent-install-bosslite-db

Starting ProdAgent after install

To start it you can use the following script %CODE{"sh"}% #!/bin/bash cd /home/mdias/prodagent/slc4_ia32_gcc345/cms/prodagent/PRODAGENT_0_12_9-cmp export PRODAGENT_ROOT=`pwd` export PATH=$PATH:`pwd`/bin export PYTHONPATH=$PYTHONPATH:`pwd`/lib export PRODAGENT_WORKDIR=/home/mdias/work export PRODAGENT_CONFIG=$PRODAGENT_WORKDIR/ProdAgentConfig.xml export MYTESTAREA=/home/mdias/prodagent source /home/mdias/prodagent/slc4_ia32_gcc345/cms/prodagent/PRODAGENT_0_12_9-cmp/etc/profile.d/dependencies-setup.sh /home/mdias/prodagent/slc4_ia32_gcc345/external/mysql/5.0.45-cmp3/bin/mysqld_safe--datadir=$PRODAGENT_WORKDIR/mysqldata --socket=$PRODAGENT_WORKDIR/mysqldata/mysql.sock --skip-networking -log-error=$PRODAGENT_WORKDIR/mysqldata/error.log --pid-file=$PRODAGENT_WORKDIR/mysqldata/mysqld.pid & prodAgentd --start %ENDCODE% You can use also

prodAgentd --status
prodAgentd --shutdown

AlpGen Production using ProdAgent

AlpGen uses a python script, cmsGen to interface with AlpGen inside CMSSW, following these steps:

• 1rst step: get information from the config file
• 2nd step: copy alpgen grid2 file
• 3rd step: split the cfg file into two files
• 4th step: make weighted events
• 5th step: make unweighted events
• 6th step: make links and providing some information

First, set up your cms environment: %CODE{"sh"}% TOP=$PWD export SCRAM_ARCH=slc4_ia32_gcc345 export BUILD_ARCH=slc4_ia32_gcc345 export VDT_LOCATION=/OSG source $VDT_LOCATION/setup.sh #Check for valid voms proxy, must be valid for at least 24hrs voms-proxy-info -exists -valid 24:00 if [ $? == 1 ] ; then voms-proxy-init -voms cms:/cms/uscms fi export X509_USER_PROXY=$(voms-proxy-info -path) # define versions project=CMSSW version=2_1_12 # set up a CMSSW area cd $TOP export SW_DIR=/home/OSG_app/app/cmssoft/cms source $SW_DIR/cmsset_default.sh ${project}_${version} scramv1 project $project ${project}_${version} cd ${project}_${version}/src %ENDCODE% Now we have to install the AlpGen :

cmsenv
export CVSROOT=:ext:mafd@cmscvs.cern.ch:/cvs_server/repositories/CMSSW
export CVS_RSH=/usr/bin/ssh
addpkg GeneratorInterface/AlpgenInterface V00-03-00-01
addpkg FWCore/Sources V00-15-01-01
cvs co -r 1.1.2.3 GeneratorInterface/AlpgenInterface/src/AlpgenExtractor.cc
scram b

• First line: alpgen (always)
• Second line: name of the executable
• Third line: name of the grid2 file (without ".grid2)
• All the rest: standard parameters, it's highly recommended not to include the seeds to avoid confusion (but it doesn't matter) About grid2 files, they MUST be in the CMSSW release. They are in this area: $HOME/CMSSW_2_1_12/src/GeneratorInterface/AlpgenInterface/data/

alpgen
wjet_0ptw100gen
w0j_0ptw100
njets 0
ebeam 7000
ih2 1
ickkw 1
iqopt 1
ptjmin 20
etajmax 5
drjmin 0.7
iwdecmode 4