Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: 'User Switching' added

...

Zero Configuration

  • The Agent is developed for has been designed to require 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 not 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.

...

  • 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

User Switching

  • The Universal Agent can switch user accounts on Windows Systems, with authentication information being stored in the Windows Credential Manager. This solution provides a secure and compliant implementation that does not require the main Agent process to be run as root.
    • Display feature availability
      StartingFromRelease1.11.4
  • See JobScheduler Universal Agent - Running jobs as a different user

Download & Installation

...