Job execution mechanism and SSH usage for AutoSys Agent

Products

• Autosys Workload Automation
• Workload Automation Agent

Issue/Introduction

This article explains the internal mechanism the AutoSys Agent uses to trigger scripts and commands on a target server and clarifies the role of SSH in job execution.

Question:
How does the AutoSys Agent trigger scripts on a client server, and is SSH used for standard command jobs?

Environment

• Product: AutoSys Workload Automation AE
• Component: System Agent (All Versions)
• Platform: Linux, UNIX, Windows

Resolution

Resolution The AutoSys Agent does not use SSH to trigger standard command or script jobs. The execution follows these steps:

1. Connection: The AutoSys Scheduler maintains a persistent connection to the Agent software installed on the target machine.
2. Instruction: The scheduler sends an instruction to the Agent to start a job.
3. Local Invocation: The Agent receives the instruction and requests the local Operating System (OS) to create a new process. On UNIX/Linux, this typically involves a fork and exec call; on Windows, it uses the CreateProcess API.
4. Monitoring: The OS manages the process. The Agent monitors the Process ID (PID) and captures the exit code and output (STDOUT/STDERR).
5. Reporting: Upon completion, the Agent reports the status back to the scheduler.

Note on SSH: SSH is only utilized for specific "Remote Execution" or "Proxy" job types and SFTP/SCP file transfers where the Agent must authenticate to a secondary remote host to perform a task.

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.