JAMS Python integration
Python Script Scheduling on Windows, Linux, and Unix
Paste Python into a JAMS Scheduler job and run it on a Windows agent, a Unix agent, or over SSH, with dependencies, alerts, and the full run history.
Three job types
PythonWindows, PythonUnix, and PythonSSH
Paste the code
No separate .py file needed
Your interpreter
Uses the Python installed on the agent
What JAMS Scheduler Runs in Python
Paste the code into the job’s Source tab, pick the agent, and set the credential it runs as. Schedules, dependencies, and alerts work like any other job.
How JAMS Scheduler Runs Python
Each Python method has a template that names the interpreter, such as #!/usr/bin/env python on Unix or the path to python.exe on Windows. Change it once on the execution method and every job uses it.
Python has to be installed on the agent that runs the job.
Requirements
Windows
JAMS Agent for Windows or the scheduler, with python.exe installed
Unix and Linux
JAMS AgentD with Python installed
SSH
JAMS AgentX with Python installed
Python Jobs in a Cross-Platform Workflow
A Python job can wait on an Airflow DAG or a SQL Server load, transform the output, and pass it to a file transfer.
When the script exits with an error, you get the same alert as any other failed job.
Python FAQ
Can I paste Python code into a JAMS job?
Yes. PythonWindows, PythonUnix, and PythonSSH all take the code directly in the job’s Source tab.
Does Python need to be installed on the JAMS server?
Only if the job runs there. Python needs to be installed on whichever agent or scheduler runs the job.
Can I run an existing .py file?
Yes. On Windows, a Command job can call python.exe with the path to your .py file.
