JAMS Ellucian Banner integration
Ellucian Banner Job Scheduling and Automation
Certified Ellucian Partner
JAMS Scheduler submits Banner jobs straight through the Banner Oracle database and pulls their .log and .lis output into the job log. Banner jobs share schedules and dependencies with everything else you run, from SQL Server loads to file transfers.
Two Banner integrations
V2 Banner Procedure, plus the original V1
Advanced Queues
Used automatically when Banner has them enabled
Kent State
182 job chains rebuilt in 26 days
What JAMS Scheduler Runs in Banner
Pick the Banner job from the list JAMS Scheduler reads out of Banner, choose a parameter set, and the job’s parameters fill in for you. Schedules, dependencies, and alerts work like any other job.
How JAMS Scheduler Connects to Banner
The V2 integration compiles one package, Z_HS_JAMS_JOBUTIL, on the Banner Oracle database and reaches it through a Banner connection in the JAMS Connection Store. Your DBA creates one role and one database user for JAMS Scheduler. The role gets execute on that package and access to a single Banner table, GJBPRUN.
If Banner has Advanced Queues enabled, JAMS Scheduler uses them with nothing to configure. If not, it falls back to dbms pipes. Proxy users work in the same [banproxy] format GURJOBS uses.
Requirements
JAMS Client and Agent
7.3 or later
Oracle Integration Pack
Required for the V2 integration
Banner database package
Z_HS_JAMS_JOBUTIL, compiled as baninst1
V1 on Unix
JAMS AgentX on the Banner application server
Banner Jobs in a Cross-Platform Workflow
A Banner job can wait for an inbound file transfer, run, then hand off to an Oracle procedure or a Crystal Reports job, all on one schedule.
Banner parameters map to JAMS parameters by number, including parameter 88. One parameter can carry several values separated by pipes.
Case Study
Kent State University Rebuilds Its Banner Schedule in 26 Days with JAMS
Kent State had 26 days between the contract award and the day its old scheduler expired. The team rebuilt all 182 job chains and went live with no contingency days.
26 days
From kickoff to production cutover
182
Job chains rebuilt by hand
Banner FAQ
Does JAMS Scheduler work with Banner Advanced Queues?
Yes. When Advanced Queuing is enabled in Banner, JAMS Scheduler uses it automatically, with nothing to configure in JAMS. Without it, JAMS Scheduler uses dbms pipes.
What’s the difference between the V1 and V2 Banner integrations?
V2 (BannerProcedure) connects directly to the Banner Oracle database and runs on the JAMS Scheduler server. V1 runs Banner’s gjajobs.shl through a JAMS agent on the Banner application server. Both are supported.
What happens if I cancel a running Banner job in JAMS?
JAMS Scheduler cancels its own job, and the job log notes that the Banner job may still be running on the host. Check the job in Banner to confirm.
