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 each Agent has to use a different port to listening for requests from a JobScheduler Master.
• Create an instance startscript for each JobScheduler Agent instance.
  

  • Display feature availability
    StartingFromRelease 1.10.2

  • Find a template jobscheduler_agent_instance.(sh|cmd)-example for an instance script in the ./bin directory of the JobScheduler Agent installation.
  • Download the templates for Unix and for Windows for previous releases.
  • Copy the template to jobscheduler_agent_<port>.(sh|cmd) where <port> is the port that the Agent is listening to.
  • The instance script includes setting the environment variables and calling the Agent start script (./bin/jobscheduler_agent.(sh|cmd)).
  • Configure the instance script with a text editor and set the environment variables that are explained in the JobScheduler Universal Agent - Installation & Operation article.
• You can start and stop etc. the JobScheduler Agent with the instance script and you will not have to use command line options such as -http-port, -ip-address, -kill-script and -java-options as they are specified by environment variables from the instance script.
• 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.
  

...