

JAMS JD Edwards integration
JD Edwards Job Scheduling and Batch Automation
JAMS Scheduler runs JD Edwards EnterpriseOne reports on Windows or Linux, on the same schedules and dependencies as the rest of your batch. A UBE can wait for a SQL Server load to finish, then start the file transfer that ships its output.
Two job types
JDEJob on Windows, JDEJobSsh on Linux
Works with
JD Edwards databases on SQL Server or Oracle
Status from JDE itself
Job status comes from the JDE Job Control table
What JAMS Scheduler Runs in JD Edwards
Each JDE job names the report, version, role, and environment, plus the JD Edwards login that starts it. Everything else, from schedules to dependencies to alerts, works like any other job in JAMS Scheduler.
How JAMS Scheduler Connects to JD Edwards
You add the JD Edwards Integration Pack with the JAMS installer, on the JAMS Scheduler and on the machine where runubexml.exe lives. One config file holds the connection string to the JDE database on SQL Server or Oracle, the bin path for runubexml, and the schema of your Master Control Table.
Each job uses two credentials: the JD Edwards login that starts the report, and the EnterpriseOne service account the job runs as. Set them up once and every JDE job reuses them.
Requirements
Integration pack
On the JAMS Scheduler and the runubexml.exe machine
JDE database
SQL Server or Oracle
Windows batch server
JAMS Agent for Windows
Linux batch server
JAMS SSH agent (an AgentX definition also works)
JD Edwards Jobs in a Cross-Platform Workflow
A JDE report takes the same schedules, calendars, dependencies, and alerts as any other job. So a nightly UBE can wait on a SQL Server job, then hand its output to a file transfer.
When a report fails or runs long, you get the same notification as any other job. Nobody has to sit on the JDE job queue to find out.

Case Study
Gold Eagle Accelerates JD Edwards Processing with JAMS
The Business Applications department at Gold Eagle is responsible for keeping Production Systems online and available throughout two shifts, supporting all JD Edwards users, and managing a half dozen third-party products that integrate with JD Edwards. With mounting issues from the native JD Edwards scheduling tool, they set out to find a solid, reliable solution.
JDE FAQ
Does JAMS Scheduler run JD Edwards jobs on Linux?
Yes. The JDEJobSsh execution method connects to the Linux batch server over SSH as the EnterpriseOne service account and runs runubexml there. JAMS Scheduler checks the job’s status with a query against the Master Control table.
What does JAMS install for JD Edwards?
The JD Edwards Integration Pack, on the JAMS Scheduler and on the machine where runubexml.exe lives. On a Windows batch server, that machine also needs the JAMS Agent for Windows.
Which JD Edwards databases does JAMS Scheduler work with?
SQL Server and Oracle. The connection string has to point at the database that holds the JDE Job Control table.







