Page History

...

• Multiple instances of the JobScheduler Agent on the same computer can be operated, e.g. for different user accounts that jobs should be executed for.
• Any number of Agent instances can be started from the same installation, however, different ports have to be used that the Agent is listening to for requests of a JobScheduler Master.
• Create an instance startscript for each JobScheduler Agent instance.
  
  • You find a template jobscheduler_agent_instance.(sh|cmd)-example for an instance script in the ./bin directory of the JobScheduler Agent installation since release 1.10.2.
  • For older releases Here you can download the templates for Unix and for Windows for releases before 1.10.2.
  • Copy this template to jobscheduler_agent_<port>.(sh|cmd) where <port> is the port that the Agent is listening to.
  • The instance script has first the setting of the environment variables and then it calls the Agent startscript (./bin/jobscheduler_agent.(sh|cmd)).
  • Configure the instance script with a text editor and set the environment variables which are already described in  JobScheduler Universal Agent - Installation & Operation.
• Now you can start and stop etc. the JobScheduler Agent with the instance script where you no longer need to use command line options like -http-port, -ip-address, -kill-script and -java-options because they are specified by the environment variables.
• On Unix you can use the instance script as a service init script in /etc/init.d or corresponding locations for an automated start-up and shutdown.
• On Windows the instance script is used to create a service for an automated start-up and shutdown.
  

...