JAMS Windows integration
Windows Job Scheduling and Batch Automation
The JAMS Agent for Windows runs batch files, commands, executables, PowerShell, and VBScript on any Windows server, under the direction of one JAMS Scheduler. Jobs on agents keep running through a scheduler failover.
Two ways to install
.msi installer or push deploy from the scheduler
Ports
77 for the agent, 773 for Sequence, Workflow, and SQL jobs
Failover-ready
Jobs on agents survive a scheduler failover
What JAMS Scheduler Runs on Windows
A Windows job is a command, a script, or a program. Pick the execution method, paste or point to the source, and set the credential it runs as. Schedules, dependencies, and alerts work like any other job.
How JAMS Scheduler Connects to Windows Servers
The agent runs as a Windows service called JAMS Agent and takes its orders from a JAMS Scheduler on another machine. Install it from the .msi, or push deploy it from the scheduler with an admin account.
Run jobs on agents rather than on the scheduler itself. In a high availability setup, the failover scheduler takes over and jobs on agents keep running.
Requirements
Agent service
Listens on port 77
Sequence, Workflow, and SQL jobs
Port 773 open on the scheduler and the agent
Push deploy
Remote admin and the admin share reachable from the scheduler
Install rights
Administrator on the agent machine
Windows Jobs in a Cross-Platform Workflow
A batch file on one Windows server can wait for a Linux script on another, then start a SQL Server load and a PowerShell cleanup job.
Moving off Windows Task Scheduler? The Task Scheduler migration page covers bringing those jobs into JAMS Scheduler.
Windows FAQ
Do I need an agent on every Windows server?
You need one on each server where jobs should run, other than the JAMS Scheduler server itself. Running jobs on agents also keeps them going during a scheduler failover.
Which ports does the JAMS Agent for Windows use?
Port 77 for communication with the JAMS Scheduler. Port 773 also needs to be open on both the scheduler and the agent to run Sequence, Workflow, or SQL jobs on that agent.
Can I install the agent without logging in to every server?
Yes. Define the agent in JAMS Scheduler, then right-click it and choose Deploy. Push deploy needs remote admin and the admin share reachable from the scheduler server.
