Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 21

changes.mady.by.user Andreas Püschel

Saved on

compared with

New Version 22

changes.mady.by.user Andreas Püschel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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.
  • See How to use Agents with Fixed Priority Scheduling and Round-Robin Scheduling

Download & Installation

...

  • Jobs and Job Chains are linked to Agents by means of Process Classes.
    • A process class is assigned an Agent.
    • A job or job chain is assigned a process class.
  • A job chain can be configured to use: 
    • A default process class for subsequent job nodes. This enables a more flexible configuration than assigning the process class to a specific job that would be used for all jobs chains.
    • A second process class for File Watching that is assigned an Agent that triggers file orders for incoming files on the Agent host.
  • see See How to execute Jobs and Job Chains with Agents

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.
  • See How to use Agents with Fixed Priority Scheduling and Round-Robin Scheduling

Migration Strategy

  • Users of the existing JobScheduler instances on platforms different from Windows and Linux are asked to consider the proposed Migration Strategy.
  • Commercial license holders of JobScheduler on platforms different from Windows and Linux can ask for our Migration Service.

...