Changes between Version 49 and Version 50 of InstallingUsingRPMS

Show
Ignore:
Timestamp:
08/19/11 11:02:57 (13 years ago)
Author:
mmamonski
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • InstallingUsingRPMS

    v49 v50  
    486486}}} 
    487487}}} 
    488  
    489 = Configuring BAT accounting cron job = 
    490 **TODO** 
     488= Configuring BAT Updater = 
     489== Installation == 
     490* install BAT from RPM 
     491{{{ 
     492  yum install qcg-bat-updater 
     493}}} 
     494== Configuration == 
     495 
     496== Further info == 
     497Usage records are sent to the main BAT server (BAT Broker) every hour by the QCG BAT Updater (acting as BAT agent). The QCG BAT Updater is started every hour via a cron job (installed in `/etc/cron.hourly/qcg-bat-updater.cron`). The QCG BAT Updater is a Java batch application that on every run: 
     498* reads jobs accounting information from the QCG-Computing database 
     499* converts it to proper XML format 
     500* sends it over ActiveMQ channel to BAT-Broker 
     501* stores id of the last  record  sent to file `/opt/plgrid/var/run/qcg-bat-updater/last.id`. 
     502The Updater logs can be found in `/opt/plgrid/var/log/qcg-bat-updater/qcg-bat-updater.log`. 
     503 
     504 
    491505= Creating applications' script space = 
    492506A common case for the QCG-Computing service is that an application is accessed using abstract app name rather than specifying absolute executable path. The application name/version to executbale path mappings are stored in the file `/opt/plgrid/qcg/etc/qcg-comp/application_mapfile`: