JAMS Unix integration
Unix Job Scheduling and Shell Script Automation
JAMS Scheduler runs shell scripts and commands on Unix servers through the JAMS AgentD service or over SSH with JAMS AgentX, and ties them to Windows, database, and ERP jobs.
Two agents
AgentD as a service, AgentX over SSH
AgentX platforms
AIX, HP-UX, Linux, and Solaris
Shebang aware
UnixScript runs whatever interpreter the first line names
What JAMS Scheduler Runs on Unix
Paste the script into the job, pick the agent, and set the account it runs as. Schedules, dependencies, and alerts work like any other job.
How JAMS Scheduler Connects to Unix Servers
JAMS AgentD runs as a background service on Linux and Unix and listens on port 77. It installs as root from an .rpm or .deb package, or from a tarball when you need a non-root install.
Where you’d rather not run a service, JAMS AgentX works over SSH. The SSHAgent execution method deploys it to AIX, HP-UX, Linux, and Solaris servers.
Requirements
AgentD
Root install from .rpm or .deb, tarball for non-root
AgentD jobs
UnixShell or UnixScript execution methods
AgentX
SSH access, deploys to AIX, HP-UX, Linux, and Solaris
Port
77 for outgoing agents
Unix Jobs in a Cross-Platform Workflow
A shell script on an AIX server can wait for a z/OS batch, then start an Oracle procedure and a file transfer.
Replacing cron? The cron migration page covers moving crontab entries into JAMS Scheduler.
Unix FAQ
Which Unix platforms does JAMS Scheduler support?
JAMS AgentX deploys over SSH to AIX, HP-UX, Linux, and Solaris. JAMS AgentD runs as a service on Linux and Unix and installs from .rpm, .deb, or a tarball.
Do I need to install an agent?
Not always. The SSH agent type connects over SSH and runs commands one at a time with nothing installed. AgentD runs UnixShell and UnixScript jobs as a service.
Can JAMS Scheduler replace cron?
Yes. Cron jobs become JAMS jobs with schedules, dependencies, and alerts. The cron migration page walks through it.
