!!Setup of a EMI workarea

This document describes the procedure required for setting up a workarea for the current release of the JobManagement products

Basic requirements are:
# The machine MUST BE installed from scratch; don't try to update a gLite build machine.
# Any configuration of VCS or ETICS access is up to the user.

!!!Setup
# Remove the DAG repository, protect any repository of SL5, check if the log4j package from ETICS is not installed, then:[@

   yum clean all
   yum install yum-protectbase.noarch

@]
# Install the EPEL extension:[@

   rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm

@]
# Install the dummy packages (just for developers), the file  /etc/yum.repos.d/emi-rpms.repo must contain:[@

[EMI]
name=EMI
baseurl=http://devel12.cnaf.infn.it:7444/repository/emi-build-ext
enabled=1

@] 
# run: [@

   yum install emi-build-environment

@]
# Install the ETICS suite:[@

   cd /opt && wget "http://eticssoft.web.cern.ch/eticssoft/repository/etics-client-setup.py" -O etics-client-setup && \
   python etics-client-setup

@]

!!!Build
The procedure for building a JobManagement subsystem is the following:[@

etics-workspace-setup
etics-get-project emi
etics-checkout --noask --platform sl5_x86_64_gcc412EPEL --continueonerror --project-config <current_project_config> -c <configuration_name> <module-name>
etics-build --platform sl5_x86_64_gcc412EPEL --continueonerror <module-name>

@]

These are the parameters for each subsystem:

|| border=1
||!module-name ||!configuration_name ||
||emi.cream-ce ||emi-cream-ce_B_1_13 ||
||emi.cream-ui ||emi-cream-ui_B_1_13 ||
||emi.wms ||emi-wms_B_3_3 ||
||emi.wms.ice ||emi-ice_B_3_3 ||
||emi.wms-ui ||emi-wms-ui_B_3_3 ||

New CE configurations (29/04/2001):

|| border=1
||!module-name ||!configuration-name ||
|| emi.cream-ce || emi-cream-ce_B_1_14 ||
|| emi.cream-ui || emi-cream-ui_B_1_14 || 

The value of the current_project_configuration is communicated by the release manager (currently, 29/04/2011, it is ''' emi_B_1_rc4''' ).

!!!known Issues
Nothing to report