This page refers to the gLite version of CREAM. For CREAM released with EMI, please refer to the new CREAM wiki: http://wiki.italiangrid.org/CREAM

These instructions affect only the old blparser, not the new one that will be introduced with CREAM CE v. 1.6 (glite-ce-blah 1.14)

The yaim configuration instructions reported here explains how to configure a CREAM CE and the BLAH blparser (old model) considering the scenario where the BLAH blparser has to "serve" a single CREAM CE.

Considering that the blparser (old model) has to run where the batch system log files are available, let's consider a scenario where there are 2 CREAM CEs (ce1.mydomain and ce2.mydomain) that must be configured. Let's suppose that the batch system log files are not available on these 2 CREAM CEs machine. Let's assume they are available in another machine (blhost.mydomain), where the blparser has to be installed.

The following summarizes what must be done:

  • In the <siteinfodef-dir>/services/glite-creamce for ce1.mydomain sets:
BLPARSER_HOST=blhost.mydomain
BLAH_JOBID_PREFIX=cre01_
BLP_PORT=33333
and configure ce1.mydomain via yaim as explained here
  • In the <siteinfodef-dir>/services/glite-creamce for ce2.mydomain sets:
BLPARSER_HOST=blhost.mydomain
BLAH_JOBID_PREFIX=cre02_
BLP_PORT=33334
and configure ce2.mydomain via yaim as explained here
  • In the <siteinfodef-dir>/services/glite-creamce for blhost.mydomain sets:
CREAM_PORT=56565
and configure blhost.mydomain via yaim as explained here (see section "Blparser configuration")
  • In blhost.mydomain edit the file /opt/glite/etc/blparser.conf setting (considering the pbs/torque scenario):
GLITE_CE_BLPARSERPBS_NUM=2

# ce01.mydomain
GLITE_CE_BLPARSERPBS_PORT1=33333
GLITE_CE_BLPARSERPBS_CREAMPORT1=56565

# ce02.mydomain
GLITE_CE_BLPARSERPBS_PORT2=33334
GLITE_CE_BLPARSERPBS_CREAMPORT2=56566

  • Restart the blparser on blhost.mydomain: /opt/glite/etc/init.d/glite-ce-blparser restart
  • Restart tomcat on ce01.mydomain and ce02.mydomain
  • You can of course replace 33333, 33334, 56565, 56566 (reported in the above examples) with other port numbers