The SCT Banner Pieces

1. The SCT Banner Pieces

2. SCT Banner Overview • SCT Banner is a mature product • Original versions built in the late 80's • Written to integrate Student, HR, Alumni, Financial Aid, and Finance information • Has had a lot of functionality added to it over the years • It is a BIG application now

3. Installed SCT Banner • Documentation set • Banner basics • Software • Directory structures • Environment variables

4. SCT Banner files • Location of other SCT Banner files and their uses • On the RDBMS server • On the Client • On the Application server (Internet Native Banner) • On the Web server (Self Service)

5. SCT Banner Documentation set • SCT Banner features a documentation set in PDF format • Install Guides • Release Guides • Upgrade Guides • A set of Technical Reference Manuals • A set of User Reference Manuals

6. Banner Documentation installation • Unloaded from the Documentation CD • Requires decryption password • File shared to end users • Directory is bdoc5x • setup5x • Server Install Guide • Client Install Guide • Bookshelf Install Guide

7. SCT Banner Documentation manuals • bdoc5x directory • Product manual directories • fin5x, alumni5x, stud5x, etc • Index directory • _index5x • Technical reference directory • trm5x • bkshlf5x.pdf • Startup page for the Banner Bookshelf

8. SCT Banner User Manuals • User Reference Manuals • Available online to all SCT Banner users • Set up through an SCT Banner form GUAUPRF • Define location of Acrobat Reader • Define location of Banner Bookshelf

9. SCT Banner Technical Manuals • Technical Reference Manuals • Available online to all SCT Banner users • Set up through an SCT Banner form GUAUPRF • Define location of Acrobat Reader • Define location of Banner Bookshelf

10. SCT Banner Basics – Naming Conventions • Software • Product modules • Product directories • Software Objects • Pro*C source code • Pro*Cobol source code • Forms binaries (FMB) • Database object source code

11. Banner Basics - Products • Software • Product modules Admin Finaid Payweb Common BANINAS Aluweb General VR-Student Wtailor Student VREpos Infoacc Arsys VRBrite Intcomp Alumni Genweb Finance Stuweb Payroll Scomweb Posnctl Facweb

12. Banner Basics – Product directories • Software • Product directories are named after the product • Each of these directories has a common set of subdirectories • c • cob • forms • dbprocs • views • plus • misc

13. Banner Basics – Compiler conventions • Software • There are different naming conventions for each type of software objects within these directories • Pro*C • *.pc - Pro*C source file • *.h - C header file • *.c - C source file • Pro*Cobol • *.pco - Pro*Cobol source file • *.cob - Pro*Cobol copylibs

14. Banner Basics – Forms conventions • Software • There are different naming conventions for each type of software objects within these directories • Forms • *.fmb - Forms binary source file • *.mmb - Menu binary source file • *.pll - Procedure Library • *.ogd - Graphics Library • *.gif - GIF files • *.ico - Icon files • *.rdf - Reports binary source file

15. Banner Basics – SQL conventions • Software • There are different naming conventions for each type of software objects within these directories • dbprocs • xxKxxxx.sql - package source code • xxPxxxx.sql - procedure source code • xxFxxxx.sql - function source code • xxTxxxx0.sql - trigger source code • views • xxVxxxx0.sql - view creation • plus - xxxxxxx.sql

16. Exercise 1 • What SCT Banner products did you purchase? • What SCT Banner products are installed? • Who has access to the Banner manuals? • Which manual discusses distributed Banner security?

17. Banner Basics – Web products • Software • There is a difference in the naming conventions used for the web products • dbprocs (cont.) • HWSKxxxx.sql/BWSKxxx.sql - Student Web package source code • HWGKxxxx.sql/BWGKxxxx.sql - General Web package source code • HWRKxxxx.sql/BWRKxxxx.sql - Finaid Web package source code • HWPKxxxx.sql/BWPKxxxx.sql - Employee Web package source code • HWAKxxxx.sql/BWAKxxxx.sql - Alumni Web package source code

18. Banner Basics – Web products • Software (continued) • TWGKxxxx.sql - Web Tailor Global package source code • BWLKxxxx.sql – Faculty Web package • BWCKxxxx.sql – Common Web package • misc • Compile scripts for Pro*C, Pro*Cobol • Other supporting web package(s)

19. Banner Basics - Objects • Database • Product owners • Product codes • Important users • Database Objects • Tables • Views • Packages (procedures and functions) • Triggers

20. Banner Basics – Product owners • Product Owners and Codes • General GENERAL G • Student SATURN S • Finance FIMSMGR F • AR TAISMGR T • Position Control POSNCTL N • Payroll PAYROLL P • FinAid FAISMGR R • Alumni ALUMNI A • Web for … WTAILOR TW

21. Banner Basics - Example • Database objects (Tables and views) • Example: G L R V R B L 1 2 3 4 5 6 7 1 - Primary Module (S- Student, G- General, F- Finance) 2 - Sub-module (L- Letter generation, G- General Person) 3 - Type of object (R- Report, A- Form, R- Repeating table) 4-7 - Meaningful name IF Pos 2 is a T and Pos 3 is a V, then the object is a validation table

22. Banner Basics - Triggers • Triggers • aT_abcdddd_xxxxxxxxxxxxxxxxxx (Total no more than 29) • a = Product identifier (S) Student, (P)ayroll • T = Trigger • abcddd = Table name • xxxxx = Meaningful trigger name

23. Banner Basics - Procedures • Database • Procedures and Functions • P_xxxxxxxxxxxxxxxxxx (Total no more than 29) • F_xxxxxxxxxxxxxxxxxx (Total no more than 29) • xxxxx = Meaningful name (Up to 27 characters) • Cursors • xxxxxxxxxxxxxxxxxxxxxxxxxxx_C

24. Banner Basics – Referential Integrity • Referential integrity • Parent/Child relationships are enforced at the database level • No child data without a referenced parent key • No deletion of parent key while child records exist

25. Banner Basics – RI example Permanent Primary Key PR Address PK_STVATYP STVATYP on Parent Table STVATYP_CODE Foreign Key 101 PR FK1_SPRADDR_INV_STVATYP_CODE on SPRADDR SPRADDR_ATYP_CODE Child Table

26. Exercise 2 • What can you tell me about the column SPRADDR_ATYP_CODE? • The package for Admissions Checklist Processing was accidentally dropped. How would you restore it? • Which product does HWSKANAM belong to?

27. Banner Basics - Installer • There is an installer (baninst) for the SCT Banner product on the RDBMS machine • Different on each platform • Modeled off of the old Oracle character mode installer • Menu interface for a bunch of shell scripts

28. Banner Basics – Unloading Banner • There is an unload and decrypt program that will unload the SCT Banner forms executable files onto a Windows machine • Requires a decryption password • After unloading forms executables, they must be copied to the final forms/file server location(s)

29. Banner Basics - BANNER_HOME • BANNER_HOME is a variable used to define the location of an SCT Banner software tree • Used by SCT Banner software as a base alias to find other SCT Banner software

30. Banner Basics - BANENV (Unix) • BANENV is a shell script that is used to manage setting of the SCT Banner variables • Modeled on the oraenv file • Usually invoked from oraenv once the desired SID is known • Other systems follow this same premise banlogic.com (VMS) registry (NT)

31. Banner Basics - Important Users • BANINST1 • Owns all the functions, packages, procedures, and views • BANSECR • Owns the SCT Banner security tables and objects

32. Exercise 3 • What schema owner should own your views? • Do you still have your original install directory?

33. Banner Installation - Software • Two CD-ROMs of SCT Banner software • Database contents and supporting code • Client forms • All software on the CD-ROMs is encrypted • Encryption Keys are on a sheet of paper shipped with the order. DO NOT LOSE! • Software is decrypted and downloaded onto RDBMS server

34. Banner Installation - Process • The SCT Banner database software is installed on the RDBMS server in several steps: • Download Software • Create SCT Banner Environment • Create SCT Banner Instance • Create SCT Banner Database Objects • Compile Pro*C and Pro*Cobol

35. Banner New Installation – Step 1 • The first step is to download the software • There are four basic steps in downloading: • Identify Products to download • Define Global Variables • Download the software • Build the environment control scripts

36. Banner New Installation – Identify products • Identify Products to download (banpswd.shl) • First, two C programs (crypfile.c and inipassr.c) must be compiled to use in decrypting the SCT Banner products • Once these are done, the install script will ask for a decrypt password • This will then build a menu with the appropriate products marked for downloading

37. Banner New Installation – Global definitions • Define Global Variables (banprmp.shl) • BANNER_HOME • EXE_HOME • ORACLE_HOME • ORACLE_SID • C • COBOL

38. Banner New Installation – Software download • Download the software (bansrce.shl) • This process will download the software from the CD • Decrypt • Decompress • Populates the following directory structure:

39. SCT Banner Software Directory Root Directory BANNER_ROOT FOCEXP_ROOT BANNER FOCEXP (BANNER_HOME) (FOCEXP_HOME) alumni alumni arsys arsys common common finaid finaid finance finance general general install install payroll payroll posnctl posnctl student student upgrades upgrades links The Banner Software Default Directory Structure

40. Banner Software Directories • BANNER_HOME • Defines the home directory of the SCT Banner products • Each product has its own directory • General is a special product • Contains executables and administrative objects • Common is used for cross-product objects • Upgrades are used to stage SCT Banner upgrades • Links directory is used to centralize process access

41. Banner General Directories general c cob dbprocs forms exe gif ico install misc plus verify views The Product Software Default Directory Structure

42. Banner Product Directories • C directory contains the Pro*C source • COB directory contains the Pro*Cobol source and Cobol copybooks • DBPROCS contains the source for database procedures, functions, triggers, and O:A functions and procedures • FORMS contains the source for the forms, libraries, menus and reports

43. Banner Product Directories • MISC directory contains the Perl scripts used on the NT platform and Shell scripts for UNIX. • On VMS the COM directory contains the DCL scripts • PLUS directory contains SQL*Plus scripts • VIEWS contains source for the database views and O:A views

44. General Directories • General directory contains some special subdirectories: • EXE contains all the executables for all products • GIF contains the .gif files used in SCT Banner • ICO contains the icon files used in SCT Banner • ADMIN and PLUS directory under General also contains administration and upgrade scripts

45. Banner New Installation – Step 2 • The install process then builds some environment manipulation scripts for managing SCT Banner variables (bansubs.shl): • banenv - for the Bourne shell • cbanenv - for the C shell • kbanenv - for the Korn shell • *banali - for printer aliasing for the various shells • Banlogic - for VMS

46. Banner New Installation – Environment creation • The next step of the install process will create an SCT Banner environment on the RDBMS server • Build the LINKS directory (banlnks.shl –UNIX only) • Update the environment (bansenv.shl) • Oraenv is then modified to point to the banenv and cbanenv files (UNIX) • Oratab is modified with the new database • Banlogic.com is modified with directory locations (VMS)

47. Banner New Installation – Step 3 • The next set of steps creates the SCT Banner database • Uses a pre-created database (bancrdb.shl, bancrtb.shl are provided for reference) • Creates the SCT Banner accounts (bancrus.shl) • Modifies the SCT Banner database configuration (baninit.shl)

48. Banner New Installation – Step 4 • The next set of steps in the NEW install will create the database objects • Import SCT Banner tables and sample data (banimp.shl) • Build SCT Banner procedures and functions (bandbpr.shl) • Import views and create synonyms (banvwsy.shl)

49. Multiple Banner environments • Multiple SCT Banner software environments • Initial install only built one code tree • Need to copy this to another tree to use as an upgrade staging area • Must manage the access to these different sets of SCT Banner code by using: • Shell scripts • Icons • DOS .bat files

50. Multiple Banner databases • Multiple SCT Banner instance databases • Initial install only built one database • Need to clone this to a training database and a production staging database • Must manage the access to these different SCT Banner databases by using: • Shell files/registry/DCL procedures • Icons • DOS .bat files