

JAMS Oracle E-Business Suite integration
Oracle E-Business Suite Job Scheduling and Automation
JAMS Scheduler runs Oracle EBS concurrent programs and request sets from drop-downs that read straight from EBS, then sequences them with jobs outside EBS.
Three job types
OracleEBSConcurrent, OracleEBSRequestSet, OracleEBSJobSsh
Agent
AgentD or AgentX on the Oracle server
Parameters
Set each concurrent program’s parameters in JAMS
What JAMS Scheduler Runs in Oracle EBS
Pick the application user, responsibility, application, and program from drop-downs that fill in from EBS. The program’s parameters appear on the job, ready to set. Schedules, dependencies, and alerts work like any other job.
How JAMS Scheduler Connects to Oracle EBS
Install the Oracle E-Business Suite Integration Pack on the JAMS Scheduler and deploy JAMS AgentD or AgentX to the Oracle server. The connection string lives on the execution method, and you can override it per folder or per job.
Jobs use an Oracle credential. If the job’s user has OS authentication to Oracle, JAMS Scheduler passes those credentials through and no separate Oracle user is needed.
Requirements
Integration pack
On the JAMS Scheduler
Oracle server
JAMS AgentD or AgentX
Connection
OEBSConnectionString on the execution method, folder, or job
Credential
An Oracle user, or OS authentication
Oracle EBS Jobs in a Cross-Platform Workflow
A month-end close request set can wait for a SQL Server load and a file transfer from the bank, then trigger the reports that follow.
If a request set fails, you get the same alert as any other failed job.
Oracle EBS FAQ
Can JAMS Scheduler run an EBS request set?
Yes. The OracleEBSRequestSet execution method runs request sets and lists each concurrent program in the set, with its parameters editable.
Can I change concurrent program parameters from JAMS?
Yes. OracleEBSConcurrent shows every parameter of the selected program on the job. OracleEBSJobSsh lets you set field values as JAMS parameters.
What do I install on the EBS server?
A JAMS agent, either AgentD or AgentX. The integration pack itself goes on the JAMS Scheduler.







