1 / 35

Using Appworx to Schedule Jobs in Banner

Using Appworx to Schedule Jobs in Banner. Joyce Feimer - IT Services Analyst and Eric Raznick- Director, ITS San Mateo County Community College District. Appworx @ SMCCD. About 27,000 students. Appworx @ SMCCD. Live with Banner 7 - Student, HR, Fin Aid, Finance,

isabelle-barrett
Download Presentation

Using Appworx to Schedule Jobs in Banner

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Using Appworx to Schedule Jobs in Banner Joyce Feimer - IT Services Analyst and Eric Raznick- Director, ITS San Mateo County Community College District

  2. Appworx @ SMCCD • About 27,000 students

  3. Appworx @ SMCCD • Live with Banner 7 - Student, HR, Fin Aid, Finance, • Other products: Xtender, SARS, Ad Astra, Hyperion (Brio), etc.. • Using Banner since version 1! • Now using IBM AIX (Unix)

  4. Appworx @ SMCCD • Why we wanted an automated Job Scheduler… • Had been on VMS for many years • Really liked “single threaded queues” • Didn’t have a lot of background in Unix shell scripts (cron is icky!) • Wanted something designed to work with Banner • Ability to monitor the jobs as they are running • You don’t have to feed it!

  5. Appworx @ SMCCD • Type of jobs we run from Appworx: • Nightly feeds (sfrfasc, sfpfaud, tgrfeed, tgrappl, furfeed, etc..) • Hourly Shell scripts (stats, moving files around) • External Application Extracts • Warehouse jobs • Daily Statistical Reports • “Clean-up” scripts • Creation of “static web pages” • Baseline Banner jobs!

  6. # 05 18 * * * /usr/local/admin/backups/dbbackup > /var/tmp/dbbackup.log 2>&1 # 09 17 * * * /untar.shl >/var/tmp/untar.log 2>&1 # 42 14 * * * /usr/local/admin/clone_PROD_PPRD.shl >/var/tmp/clone_PPRD.log 2>&1 # 39 17 * * * su - oracle -c /u09/exports/impPROD.shl >/u09/impPROD.log 2>&1 # 54 16 * * * su - oracle -c /u01/oracle/admin/PROD/create/PROD.sh >/u01/tmp/PRO D.log 2>&1 #end Colby # # Ted - PPRD no longer on LUCY since ban7 go LIVE! # Clone PPRD on Sunday using the most resent backup ##00 07 * * 0 /usr/local/admin/backups/rman_dbdup0_pprd.shl >/usr/local/admin/lo gs/rman_dbdup0_pprd.log 2>&1 # # # Check for posting errors 5,25,45 8-19 * * 1-6 su - operfin -c "/usr/local/admin/chk_posting.shl PROD" >/v ar/tmp/chk_posting.log 2>&1 # # Restart Finance SleepWake to load output files into database for review 00 11,15 * * * su - operfin -c "/usr/local/admin/restart_slwk_db.shl PROD" >/var /tmp/restart_slwk_db.log 2>&1 # # Stop the Finance SleepWake processes 00 22 * * * su - operfin -c "/usr/local/admin/stop_slwk_db.shl PROD" >/var/tmp/ Unix Cron File

  7. Creating a Module

  8. Define the library

  9. Define Program Type

  10. Define Output

  11. Define Prompts

  12. Edit Prompts

  13. Edit Prompts

  14. Define Schedule

  15. Chains

  16. Expanded Chain

  17. Predecessor - Success

  18. Predecessor - Complete

  19. Frequency of Runtimes

  20. Frequency setup

  21. Daily Reoccurring Jobs

  22. Create Exceptions

  23. Ad Hoc Submission

  24. Enter Prompts & Options

  25. Submit job to run

  26. Successful Finish

  27. Output Files

  28. Output - Log files

  29. Emailed Output

  30. Unsuccessful Finish

  31. Log File of Failed Job

  32. Viewing Output Files • We licensed a small program called RptView (Report Viewer) for Windows from Drec Software • Looks like “greenbar”! • Contact Info: • http://www.drecsoftware.com/

  33. Output – List files

  34. Important Things to Know… • If you copy the database – be careful… • In Chains - consideration of the “Predecessor” Actions are really important! (Success, Failure, Complete, etc) • Does not use the path statement the same way – you need to make sure you are pointed at the right version of executables.

  35. Questions???Suggestions??? Many thanks from Eric & Joyce raznick@smccd.edu feimer@smccd.edu

More Related