JAMS Apache Airflow integration
Run Apache Airflow DAGs Inside Enterprise Workflows
JAMS Scheduler triggers your Airflow DAGs, polls them until they finish, and makes them wait on ERP, database, and file jobs that live outside Airflow.
Execution method
Airflow
Status checks
Every 5 seconds by default, down to 1
Needs
JAMS 7.8.3 or later and HTTPS on Airflow
What JAMS Scheduler Runs in Airflow
Pick the connection, then choose the DAG from a list. JAMS Scheduler triggers it, checks its status, and writes the details to the job log. Schedules, dependencies, and alerts work like any other job.
How JAMS Scheduler Connects to Airflow
JAMS Scheduler uses version 2 of the Airflow REST API over HTTPS. Store the server, port (8080 by default), and login in a Connection Store item and reuse it across jobs.
If Airflow uses a self-signed certificate, install it on the JAMS Scheduler and on any agents that run Airflow jobs.
Requirements
JAMS version
7.8.3 or later, Scheduler and Client
Airflow API
REST API v2 over HTTPS
Certificate
An x.509 certificate trusted by JAMS
Port
8080 by default
Airflow DAGs in a Cross-Platform Workflow
Keep Airflow if your data team owns the DAGs. JAMS Scheduler can make a DAG wait for an SAP or SQL Server job, then hand off to a file transfer when it finishes.
If you’d rather move the DAGs themselves into JAMS Scheduler, the Airflow migration page covers that path.
Airflow FAQ
Can JAMS Scheduler trigger an Airflow DAG?
Yes. The Airflow execution method lists your DAGs, triggers the one you pick, and monitors it until it finishes.
How does JAMS know when a DAG run finishes?
It polls the Airflow REST API, every 5 seconds by default. You can lower that to 1 second, but low intervals add load to the Airflow server.
Which JAMS version supports Airflow?
JAMS 7.8.3. Both the JAMS Scheduler and the JAMS Client need to be on 7.8.3 or later.
