This document describes how to configure and install job agents.Contents
A job agent is a program running on another computer that is regularly checking the BASE job queue for jobs that are awaiting execution. When the job agent finds a job that it is able to execute it loads the plugin and executes it.
A job agent supports lots of configuration options that are not supported by the internal job queue. For example, you can:
All these options make it possible to create a very flexible setup. For example one job agent can be assigned for importing data only. Another job agent can be assigned for running analysis plugins for specific project only. A third may be a catch-all job agent that does all low-priority jobs.
It is not very difficult to install a job agent, but it requires some manual configuration. Therefore, no job agent is installed by default. Here is how to do it:
jobqueue.internal.enabledshould be changed to
falsefor the web server. This setting is found in the
www/WEB-INF/classes/base.configfile. After you have changed the setting the web server must be restarted.
jobagent.propertiesfile in step 2.3.3 below.
GRANT ALL ON base2.* TO firstname.lastname@example.org IDENTIFIED BY 'password'; GRANT ALL ON base2dynamic.* TO email@example.com;Replace
job.agent.hostwith the host name of the server that is going to run the job agent. You should also change the password. This password goes into the
base.configfile in step 2.3.2 below.
www/WEB-INF/classes/base.configfile must be configured to use the same database as the web server application. The most important settings are:
www/WEB-INF/classes/jobagent.propertiesfile contains settings for the job agent. The most important ones to specify value for are:
jobagent.properties file contains many more configuration
options. See the
reference for more information.
bindirectory, register the job agent with
bindirectory, start the job agent with
./jobagent.sh start &
See the jobagent.sh reference for more information about what you can do with the command line interface.
Before the job agent starts executing jobs for you it must be configured. The configuration is done through the web interface.
Administrate -> Plugins -> Job agentsmenu.
Pluginstab you can specify which plugins the job agent should handle. Note that if you have installed external plugins on the web server, those plugins must be installed on the job agent as well. It is possible to specify different paths to the JAR file for each job agent.
Sharefunctionality to specify which users/groups/projects should be able to use the job agent. You must give them at least