Agentless Scheduling

Introduction

SSH (Secure Shell File Transfer Protocol) allows a JobScheduler to execute programs on another computer without a JobScheduler Agent being installed on that machine.

• The beauty of SSH is its simplicity. It allows public/private key authentication and is well suited to execute programs for specific accounts.
• The ugly side of SSH is that there is limited control of child processes on the remote host. 
  • If during an SHH session a number of child processes has been spawned by a program and that SSH session gets killed then these child processes would continue to run.
  • JobScheduler provides some intrinsic means to control the behaviour of child processes in SSH sessions when using the JITL Job, see Job SOSSSHJob2JSAdapter - Handling StdErr and ExitCode

Resources

Feature in detail

How To ... Instructions

Frequently Asked Questions

Examples in detail

See also

• See our What is the difference between SSH job execution and remote JobScheduler Agents? article for more information