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.

SSH allows execution on Windows and Unix systems.

• The elegance of SSH is its simplicity. It allows public/private key authentication and is well suited to execute programs for specific accounts.
  • In addition the JobScheduler SSH JITL job allows SSH scripts to return values to the JobScheduler order as parameters. See How To - Usage of the SSH Job (SOSSSHJob2JSAdapter) with JCraft's JSch.
• One of the restrictions of standard SSH connections 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 a method for monitoring SSH jobs that allows both remote sessions and local JobScheduler tasks to be terminated - see How To - SSH Session Management for more information.
• JobScheduler provides a means of controlling the behavior of standard error output and exit codes of shell commands using the JITL SSH Job, see Job JobSchedulerSSHJob - Handling StdErr and ExitCode for more information.

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