Page History

The JobScheduler Universal Agent provides a number of unique features.

...

• The Agent is developed for zero configuration:
  • An Agent is not configured for a specific Master. Instead the Agent serves requests from any Master and is addressed by Process Classes of a Master.
  • No Agent configuration is required.
• Easy Deployment
  • Deploying the Agent to hundreds of servers is a task of minutes.
  • JobScheduler can be used to automate the deployment of Agents. Alternatively popular tools such as Puppet® can be applied.

Agent Clustering

• A number of JobScheduler Agents can be configured in an Agent Cluster for redundancy and fail-over of Agents.
• Fixed Priority Scheduling
  • JobScheduler Master will select the first available Agent for execution of jobs. 
  • If an Agent is not available then the next available Agent is selected from the Agent Cluster.
• Round-Robin Scheduling
  • JobScheduler Master switches the Agent for each job execution. 
  • If an Agent is not available then the next available Agent is selected from the Agent Cluster.

... read more

Job and Job Chain Execution

...

• To perform simple availability checks see How to perform active checks with a System Monitor such as Nagios/op5
• For more elaborate monitoring of jobs and job chains see JobScheduler Monitoring Interface - Overview

Licensing

The JobScheduler Universal Agent comes with a commercial license, for more information see Usage for Open Source Users and Commercial License Holders

• For use without an agent-specific license key the Agent will behave as follows:
  
  • it will start a task if it is not currently running any other tasks;
  • it will deny start of the task with an error message if it is already are running any other tasks;
  • if configured, an e-mail will be sent with the licensing error;
  • the job's state text will show the licensing error.
• This single-task mode allows Open Source users to install and to try the Agent's full functionality. However, a commercial license key for the Agent has to be purchased for enterprise usage, when execution of a number of parallel tasks is required.

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1482

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1483