You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

The JobScheduler Universal Agent provides a number of unique features.

Platforms and Operating Systems

The Agent can run on any platform and operating system that provides a Java Virtual Machine. No additional prerequisites apply. 

  • The Agent is developed with Scala and Java. The only requirement is a Java Runtime Environment starting from version 1.8.
  • For details on tested platforms see Platform Support

Zero Configuration

  • 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.

Remote File Watching

The JobScheduler Universal Agent can be used to watch incoming files and to trigger a job start for each file. The configuration of file order sources is effected on the JobScheduler Master.

... read more

Job Execution

The Universal Agent runs practically all JITL Jobs that previously have been executed on the Master JobScheduler. The Classic JobScheduler Agent was restricted to run mainly shell scripts.

... read more

Cross-platform Scheduling

Job chains can include jobs for execution on different Agents. This allows to define job chains with each job being executed on a different platform and passing results to subsequent jobs.

... read more

Running inside a Docker Container

JobScheduler Universal Agent inside a Docker container allows to run multiple services inside a Docker container and to start additional processes.

... read more

Communication & Security

The communication between Master and Agent is bundled in a single HTTP connection. No additional ports or firewall settings are required, the Classic Agent required extra ports to be opened. This allows HTTPS connections to be used with an intermediate reverse proxy which includes verification of certificates.

... read more on HTTP communication

... read more on Secure HTTPS Communication

Monitoring

The Agent can be monitored by use of a System Monitor. Direct support is provided for popular products such as Nagios/op5 . 

 

Pages


 
 

Navigation


  • No labels