

JAMS Linux integration
Linux Job Scheduling and Shell Script Automation
JAMS AgentD runs your shell scripts as a Linux service, installed from an .rpm or .deb package. Linux jobs get the same schedules, dependencies, and alerts as everything else JAMS Scheduler runs.
Packages
.rpm for Red Hat and SUSE, .deb for Debian
Two script methods
UnixShell and UnixScript
Or over SSH
JAMS AgentX and SSH agents
What JAMS Scheduler Runs on Linux
Paste the script into the job, pick the agent, and set the account it runs as. Everything else, from schedules to dependencies to alerts, works like any other job.
How JAMS Scheduler Connects to Linux
AgentD installs as root from the JAMS repository: .rpm for Red Hat and SUSE, .deb for Debian. Use the tarball for a non-root install. The agent listens on port 77.
It’s managed with jams-agentd commands to start, stop, restart, and report status, and it keeps its logs in /var/log/jams.
Requirements
Install
Root, from .rpm or .deb
Non-root install
Tarball, .tgz
Port
77
Job types on AgentD
UnixShell or UnixScript
Linux Jobs in a Cross-Platform Workflow
A Linux ETL script can wait on a Windows export, then start a Python job and a file transfer.
Moving off cron? The cron migration page covers it.
Linux FAQ
Do I need an agent on every Linux server?
To run script jobs as a service, yes: install AgentD on each server. For one-off commands, an SSH agent can connect with nothing installed.
Which Linux distributions have packages?
AgentD ships as .rpm packages for Red Hat and SUSE and .deb packages for Debian, with separate Red Hat builds for each release. A tarball is available for non-root installs.
Can JAMS Scheduler replace cron?
Yes. Cron jobs become JAMS jobs with schedules, dependencies, and alerts. The cron migration page walks through it.







