The sct banner pieces
1 / 130

The SCT Banner Pieces - PowerPoint PPT Presentation

  • Uploaded on

The SCT Banner Pieces. 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.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about ' The SCT Banner Pieces' - mandy

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

Sct banner overview
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

Installed sct banner
Installed SCT Banner

  • Documentation set

  • Banner basics

  • Software

  • Directory structures

  • Environment variables

Sct banner files
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)

Sct banner documentation set
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

Banner documentation installation
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

Sct banner documentation manuals
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

Sct banner user manuals
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

Sct banner technical manuals
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

Sct banner basics naming conventions
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

Banner basics products
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

Banner basics product directories
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

Banner basics compiler conventions
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

Banner basics forms conventions
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

Banner basics sql conventions
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

Exercise 1
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?

Banner basics web products
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

Banner basics web products1
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)

Banner basics objects
Banner Basics - Objects

  • Database

    • Product owners

    • Product codes

    • Important users

    • Database Objects

      • Tables

      • Views

      • Packages (procedures and functions)

      • Triggers

Banner basics product owners
Banner Basics – Product owners

  • Product Owners and Codes

    • General GENERAL G

    • Student SATURN S

    • Finance FIMSMGR F


    • Position Control POSNCTL N

    • Payroll PAYROLL P

    • FinAid FAISMGR R

    • Alumni ALUMNI A

    • Web for … WTAILOR TW

Banner basics example
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

Banner basics triggers
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

Banner basics procedures
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

Banner basics referential integrity
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

Banner basics ri example
Banner Basics – RI example


Primary Key






Parent Table


Foreign Key







Child Table

Exercise 2
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?

Banner basics installer
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

Banner basics unloading banner
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)

Banner basics banner home
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

Banner basics banenv unix
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 (VMS)

    registry (NT)

Banner basics important users
Banner Basics - Important Users


    • Owns all the functions, packages, procedures, and views


    • Owns the SCT Banner security tables and objects

Exercise 3
Exercise 3

  • What schema owner should own your views?

  • Do you still have your original install directory?

Banner installation software
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

Banner installation process
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

Banner new installation step 1
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

Banner new installation identify products
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

Banner new installation global definitions
Banner New Installation – Global definitions

  • Define Global Variables (banprmp.shl)


    • EXE_HOME



    • C

    • COBOL

Banner new installation software download
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:

Sct banner software directory
SCT Banner Software Directory

Root Directory






























The Banner Software Default Directory Structure

Banner software directories
Banner Software Directories


    • 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

Banner general directories
Banner General Directories














The Product Software Default Directory Structure

Banner product directories
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

Banner product directories1
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

General directories
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

Banner new installation step 2
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

Banner new installation environment creation
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

    • is modified with directory locations (VMS)

Banner new installation step 3
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)

Banner new installation step 4
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)

Multiple banner environments
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

Multiple banner databases
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

Banner default databases seed
Banner Default Databases - SEED

  • Out-of-the-box SCT Banner

  • Used to run new SCT Banner upgrades against first

  • Upgrade issues are then SCT issues

  • Work out the details before upgrading production database

Banner default databases trng
Banner Default Databases - TRNG

  • Used for implementation training

  • Out-of-the-box SCT Banner with some additions

    • Training user accounts

    • Training data

  • Usually cloned from SEED

Banner default databases pprd
Banner Default Databases - PPRD

  • Used for implementation and conversion

  • Out-of-the-box SCT Banner with some deletions

    • Most SEED data is cleaned out of the database

  • Used to build the Production database

  • Should be backed up as soon as users start populating validation and rule tables

Exercise 4
Exercise 4

  • You’ve just upgraded Oracle – will you be able to compile Pro*C and Pro*Cobol?

  • Does the Banner installer itself set up the Job Submission user ID and directory?

  • What user IDs do your users use when logging into the PPRD database?

Banner environment
Banner environment

  • Multiple SCT Banner environments will need both Oracle and SCT Banner variables set

    • .profile or .login calls oraenv (UNIX)

    • calls (VMS)

    • ORAENV sets: sets:

      • ORAENV_ASK --




Banner environment others
Banner environment - Others

  • VMS

    • Command procedural calls:



  • NT/Win2000

    • Path environment

    • Registry

Banner environment variables
Banner environment variables

  • Based on the SID, the appropriate environment file is called

    • BANENV/Registry sets: BANLOGIC sets:







Banner database performance
Banner database performance

  • Management of an SCT Banner database involves proactively managing:

    • Memory

      • Are your users complaining?

      • Is your system page-faulting?

      • Running SQL scripts to maintain the system

    • Disk storage

      • Fragmentation

    • Database objects

      • Invalid state

Banner database administration
Banner Database Administration

  • Close relationships with the System and Network staff

    • Patches and upgrades are maintained

    • Backup and recovery in place

    • Network access

  • It also involves being able to:

    • Create databases

    • Clone databases

    • Upgrade all Oracle software

      • “How to have a life and be a DBA also”

Banner memory management
Banner - Memory Management

  • SCT Banner moves a lot of data and involves a lot of code

    • OLTP vs. DSS

  • This means that the DBA must take an active stance on monitoring and managing SCT Banner's use of memory

    • Checking the SGA:

      • How often does the database get data from disk vs. memory?

      • How often are the stored packages accessed?

Oracle memory management
Oracle - Memory Management

  • The main areas the DBA must be concerned with are:

    • Data Base Buffers - v$sysstat

    • Shared pool - pins and gets

    • Redo logs - Checking the alert logs, v$sysstat

    • Data Dictionary cache - v$rowcache

    • Library cache - v$librarycache

    • Sort Areas - temporary tablespace

Banner storage management
Banner - Storage Management

  • SCT Banner databases take active storage management

  • Tables grow constantly

  • Indexes become unusable

  • Database use causes problems like storage fragmentation and row chaining

  • New tables with upgrades

Oracle storage management
Oracle - Storage Management

  • The storage management tasks the DBA will be most heavily involved in are:

    • Tablespace growth

    • Table sizing

    • Rollback segment sizing

    • Restructuring the database

      • Resizing/moving tables and indexes

      • Tablespace placement

      • RAID vs. non-RAID

Banner disk storage management
Banner – Disk Storage Management

  • RAID

    • Important to have for an Oracle system

    • Jbod – Lowest data cost – low overhead

    • 0 – low data cost – load balancing

    • 0, 0+1 – high data cost – most expensive

    • 5 – Highest data cost – safe

      • It takes four I/Os for one write (read data, read parity,write data, write parity)

      • Minimum of three disks, plus 66-87% of space

      • The more disks, the higher the gain

      • Not good with REDO – Sequential vs random writes

Banner object management
Banner - Object Management

  • SCT Banner is installed in one tablespace, usually named DEVELOPMENT

  • Can be divided into many tablespaces as required by the institution

    • Access reasons

    • Performance reasons

    • Maintenance reasons

    • Multi-institution reasons

Banner utilities
Banner utilities

  • SCT-supplied data catalog tool GURPDED

    • Run through Job Submission

  • SCT-supplied tool called GURRDDL

    • Used to resize tables

    • Used to resize indexes

    • Handles the referential constraints

    • Handles the permissions

    • Handles the synonyms

    • Can be used to move one or many tables

Oracle fragmentation
Oracle fragmentation

  • Databases can fragment, even with the best of software

  • Fragmentation causes performance problems

  • Tools are being developed to perform background defragmentation

  • Most common method of defragmentation is export/import

Oracle locally managed tablespaces
Oracle locally managed tablespaces

  • Oracle is moving towards a methodology that will reduce table management

  • Uses a few basic extent sizes for each tablespace

  • Tables are grouped into tablespaces according to size and growth characteristics

Banner general object management
Banner – General object management

  • There are sets of scripts provided with SCT Banner that are used to compile/recompile database objects

    • General Packages, Procedures, Functions, and Triggers

      • /sct/banner/general/dbprocs/gendbpr.sql

    • General Views

      • /sct/banner/general/views/genview.sql

Banner student object management
Banner – Student object management

  • There are sets of scripts provided with SCT Banner that are used to compile/recompile database objects

    • Student Packages, Procedures, Functions, and Triggers

      • /sct/banner/student/dbprocs/studbpr.sql

    • Student Views

      • /sct/banner/student/views/stuview.sql

Banner object management utility
Banner - Object management utility

  • SCT-supplied tool called GURALTR

  • Searches database for invalid objects and builds a recompile script

    • Used to recompile database objects (not sys nor system)

      • Packages

      • Package Bodies

      • Triggers

      • Procedures

      • Functions

Exercise 5
Exercise 5

  • How many different Banner code trees does your oraenv script handle?

  • What is the purpose of the BANNER_LINKS directory?

  • Even though studbpr.sql is in the Student product directory, what schema owner owns the database procedures in this script?

Compiling invalid objects
Compiling invalid objects

  • Run utlrp.sql as SYS to compile ALL database objects

  • Use GURALTR to recompile ALL non-SYS and non-SYSTEM database objects

  • BANINST1 owns the database packages, procedures, functions and views

    • Use GURALTRB to recompile BANINST1 objects

    • Run multiple times for dependencies

  • After manipulating ANY database objects, run GURALTR to fix any broken dependencies

Banner database triggers
Banner database triggers

  • BANINST1 does not own the database triggers

    • Each product owner owns their respective set of database triggers

    • Compile scripts for the triggers are located in the product's dprocs directory in the xxxdbpr.sql file

    • Must use these in conjunction with GURRDDL when rebuilding tables

Banner administrative software
Banner administrative software

  • There is an administrative directory for SCT Banner on the RDBMS server

  • $BANNER_HOME/admin

    • Banenv (UNIX/NT)

    • Banlogic (VMS)

    • profile.ban

    • upcase.shl

  • $BANNER_HOMEHadmin/v6/oratools

Banner non database related software
Banner non-database related software

  • SCT Banner also requires management of all the software outside of the database

    • Executable compiles

      • Pro*C

      • Pro*Cobol

    • SQL*Plus scripts

    • SQL*Loader scripts

Banner pro c 1
Banner Pro*C - 1

  • Each product owner may have a set of Pro*C programs

  • Located in /sct/banner/<product>/c

    • Based on old Oracle RPTs

    • Ugly but consistent design

  • .h - Header files (General/c only)

    • guarpfe.h - Routines for RPT emulation

    • guastdf.h - Routines for C print formatting

Banner pro c 2
Banner Pro*C - 2

  • .c - C source files (General/c only)

    • guarpfe.c - Routines for RPT emulation

    • guastdf.c - Routines for C print formatting

    • guaorac.c - Routines for Oracle interface

  • .pc - Pro*C source files

    • gurjobs.pc - Job Submission Pro*C program

    • gjrrpts.pc - SCT Banner Reports print program

Banner pro c 3
Banner Pro*C - 3

  • The compile scripts for each product's set of Pro*C programs are in the corresponding MISC directory (the same applies for OVMS and NT)

    • General Pro*C

      • /sct/banner/general/misc/gencmplc.shl

    • Student Pro*C

      • /sct/banner/student/misc/stucmplc.shl

    • Finance Pro*C

      • /sct/banner/finance/misc/fincmplc.sql

Banner pro cobol 1
Banner Pro*Cobol - 1

  • Each product owner may have a set of Pro*Cobol programs

  • Located in /sct/banner/<product>/cob

  • /sct/banner/general/cob also contains the Pro*Cobol copylibs

  • *.pco - Pro*Cobol source files

Banner pro cobol 2
Banner Pro*Cobol - 2

  • The compile scripts for each product's set of Pro*Cobol programs are in the corresponding product MISC directory

    • General Pro*Cobol

      • /sct/banner/general/misc/gencmpl.shl

    • Student Pro*Cobol

      • /sct/banner/student/misc/stucmpl.shl

    • Finance Pro*Cobol

      • /sct/banner/finance/misc/fincmpl.sql

Banner sql plus
Banner SQL*Plus

  • SCT Banner also has SQL*Plus scripts that are used by the various SCT Banner products

  • Located in: /sct/banner/<product>/plus

  • General also has some scripts that are used for admin and upgrade purposes





Banner sql loader
Banner SQL*Loader

  • SCT Banner also has SQL*Loader scripts that are used to load outside data

    • Test scores

    • EDI

  • Located in: /sct/banner/<product>/loader

    • *.ctl - SQL*Loader control files

Exercise 6
Exercise 6

  • Run the $BANNER_HOME/admin/V6/oratools/freebyte.sql script. How many free, used, and total bytes are in the development tablespace in the TRNG database?

  • What is the fully qualified name of the script to compile the GSASECR.fmb file?

Banner access methods
Banner - Access methods

  • Considerations need to be made for:

    • Access to the SCT Banner system

      • Database(s)

      • Forms

      • Report output

    • User vs. developer access

    • SCT Banner System vs. SQLPLUS

    • Microsoft Access

Creating an sct banner database
Creating an SCT Banner Database

  • Production databases are usually created sometime after the initial SCT Banner installation by the site

  • Memory sizes, block size, disk storage requirements, network considerations, and user load must be taken into account when configuring the production database

Banner database creation methods
Banner Database creation methods

  • Creation is done through one of the many tools available

    • Command line method has more creation flexibility

    • GUI mode (orainst) is easier, but requires modification before the SCT Banner data can be loaded

Cloning a banner database oracle7 8i
Cloning a Banner Database – Oracle7/8i

  • Cloning is done through a database recovery mechanism

    • Database files are copied to new directory structure

    • Produce a control file re-creation script by issuing as sys:

      • alter database backup controlfile to trace;

    • New instance is “recovered” using modified control file, and new control files are created

Cloning a banner database oracle 8i 9i
Cloning a Banner Database – Oracle 8i/9i

  • Use RMAN to make a backup of the source database

  • The clone database is created and opened NOMOUNT

  • Run the duplicate command in RMAN to perform the clone

  • The procedure is fully documented in the 'Backup and Recovery' section of the Oracle 8i Administrators Guide

Sct banner backup strategies
SCT Banner -Backup Strategies

  • Cold backups

    • Involves taking the database offline

    • Should be performed occasionally

  • Online backups

    • Oracle has very good recovery mechanisms

    • Allows the database to remain in service

    • With RMAN, backup and recovery can be completely automated

Exercise 7
Exercise 7

  • Why is the method used to clone Oracle7 databases not a good one for Oracle8 databases?

  • What is your current backup strategy?

  • Is it documented?

Self service banner ssb products
Self Service Banner (SSB) Products

  • The SCT Self Service Banner … products are an add-on set of software functionality

  • Provides a self-service browser interface to many SCT Banner functions

  • Is not “Internet Native” Banner

  • Customizable look and feel

  • Rules-defined access and display

Self service banner services
Self Service Banner services

  • Implemented by using database packages and procedures

  • Generates dynamic HTML pages from the database

  • Uses Oracle’s 9iAS Mod_plsql

  • Uses Oracle's PL/SQL Toolkit package

  • Has an administrative tool called Web Tailor


  • The end user guides are available through Banner Bookshelf through the Product User Manuals

  • The Upgrade Guides and Release Guides are available through Banner Bookshelf

  • Each product has its own set of Guides

  • Web Tailor has its own set of Guides

Self service banner software install
Self Service Banner Software Install

  • SCT Self Service Banner… installs are done on the SCT Banner RDBMS server

  • Packages are built in the database

  • The software is installed in Web for product directories

    • /sct/banner/aluweb

    • /sct/banner/facweb

    • /sct/banner/genweb

    • /sct/banner/payweb

    • /sct/banner/scomweb

    • /sct/banner/stuweb

    • /sct/banner/wtlweb

Self service banner software structure
Self Service Banner Software Structure

  • Each SCT Self Service Banner … product directory contains some of the following structure:

    • c - C programs used in web applications

    • dbprocs - Web packages

    • gif - graphics objects for buttons

    • html - Product web pages

    • misc - Web administrative scripts

Self service banner install
Self Service Banner Install

  • There is no SCT Banner install on the web server

  • The server is configured to connect to the SCT Banner database through Oracle Net

  • PL/SQL Toolkit is loaded into the database

  • Web For … .gif and .htm files are copied from the database server to the web server

  • An Apache listener is created to present the initial page for general access to the SSB system, homepage.htm

Self service banner web server install
Self Service Banner Web Server Install

  • From the web server, for each SCT Banner instance:

    • Create a DAD (Database Access Descriptor)

      • Created with Oracle’s 9iAS DAD Gateway GUI tool

      • Uses a generic username/password/connect descriptor that logs into the database on behalf of the SSB user

    • http://host:port/pls/admin_/gateway.htm, where host is your complete host name or IP address

Gateway htm

  • Click on Gateway Database Access Descriptor Settings

  • Enter

    • DAD Name: SID_SSB

    • Schema Name: www_user

    • Oracle User Name: www_user

    • Oracle Password: u_pick_it

    • Oracle Connect String: SID

  • Click Apply

  • Repeat for each database.

Pl sql toolkit
PL/SQL Toolkit

  • Install the latest PL/SQL Toolkit patch into Oracle 9iAS.

  • Apply the same level toolkit into each database by running a provided script in $ORACLE_HOME\Apache\modplsql\cfg

    • Owaload.sql

Self service banner web server directories
Self Service Banner Web server directories

  • Copy .gif and .htm files for each product from the directories on the RDBMS server to the appropriate directory on the web server:

    • /sct/banner/*web/gif 

      • /sct/ssb/SID/*gifs

    • /sct/banner/*web/htm 

      • /sct/ssb/SID/*help

Self service banner web server listener
Self Service Banner Web Server listener

  • Configure the Web server to ‘serve up’ SSB

  • Create the HTTP listener

    • Set DocumentRoot and <Directory to the /sct/ssb/SID directory

    • Set Port to the Port that the users will use

    • Set Listen to the Port that Apache will listen for

    • Set DirectoryIndex to hompage.htm

Self service banner homepage htm
Self Service Banner homepage.htm

  • The next step is to set up the homepage.htm file

    • Copy from:


    • To:


    • Replace //your server name:port/test/owa/ with your site's Mod_plsql reference and DAD

      • i.e. //bandev:8080/pls/SEED/

Self service banner web server
Self Service Banner Web Server

  • There are links that must be built in the Web tailor product to point to your institutions specific sites (Alumni, Admissions, campus directory, etc)

  • It is recommended to have a dedicated web server for SSB

  • Apply the latest Apache and/or 9iAS security and update patches

    • As of August, 2003


      • Mod_plsql

      • Jserv Rollup #3

Self service banner objects
Self Service Banner Objects

  • The only SCT Banner software to manage on the web server are the web objects needed by the Web For … products

    • .gif files

    • .htm files

    • Web Tailor image files

  • These will be updated as new versions come out

Self service banner rdbms software
Self Service BannerRDBMS Software

  • There are sets of scripts provided with SCT Banner that are used to compile/recompile database objects

    • Stuweb Packages, Procedures, Functions, and Triggers

      • /sct/banner/stuweb/dbprocs/hstudbpr.sql

    • Genweb Packages, Procedures, Functions, and Triggers

      • /sct/banner/genweb/dbprocs/hgendbpr.sql

Self service banner client
Self Service Banner Client

  • Netscape 4.x

  • Explorer 5.x/6.x

  • Generally, stay a release or two back from the latest and greatest browsers

  • Supports other browsers (opera, mozilla)

  • Can use Windows 95 up to the latest

  • Can use MacOS

Exercise 8
Exercise 8

  • From where is each web page generated?

  • How would you reload the PL/SQL toolkit in the database?

  • What SCT Banner software must be on the Web server?

Internet native banner parts
Internet Native Banner Parts

  • In Internet Native Banner, the Oracle runforms software has been modified to run in two parts:

    • The runform engine running on an application server

    • A Java applet that performs the display and data entry tasks

  • The forms server then “tags up” the SCT Banner forms before delivering

Internet native banner products
Internet Native Banner Products

  • There are two products involved:

    • The Apache web server utilizing servlet technology

    • The Oracle Forms web runtime engine (included in 9iAS)

  • Apache handles the HTTP(S) connection request to SCT Banner

  • The Oracle Forms web runtime engine handles the forms management

Internet native banner installs
Internet Native Banner - Installs

  • There are two supported ways to install this:

    • Oracle 9iAS http server-only installation, plus the Forms and Reports 6i server

  • Plus patchset 13 for Oracle Forms and Reports 6i

    • 9iAS Enterprise Edition

      • Plus patchset 13 for Oracle Forms and Reports 6i

Inb files to be modified
INB – files to be modified

  • D:\ORACLE\iSuites\Apache\Apache\conf\httpd.conf

    • Apache listener configuration

  • D:\ORACLE\iSuites\Apache\Jserv\conf\

    • Servlet engine classpath

  • D:\ORACLE\iSuites\Apache\Jserv\servlets\

    • Forms servlet initializaion

  • D:\ORACLE\806\forms60\server\formsweb.cfg

    • Forms servlet configuration file

  • D:\ORACLE\806\conf\6iserver.conf

    • Virtual path definitions for web forms

  • D:\ORACLE\806\forms60\server\default.env

    • Environment variables for the FORMS and REPORTS servlets

Inb httpd conf
INB – httpd.conf

  • Configure the Web server to ‘web up’ INB

  • Edit the HTTP listener

    • Set DcumentRoot and <Directory to the D:\sct\inb\SID directory

    • Set Port to the Port that the users will use

    • Set Listen to the Port that Apache will listen for

Inb zone properties and jserv properties
INB – and


    • servlet.SID.code=oracle.forms.servlet.ListenerServlet

    • servlet.SIDD.initArgs=envfile=d:\sct\ssb\seed\conf\seed.env


    • # Oracle Forms and Reports Servers

    • wrapper.classpath=D:\ORACLE\806\forms60\java\f60srv.jar

    • wrapper.path=D:\oracle\isuites\bin;D:\ORACLE\806\bin

Inb formsweb cfg
INB – formsweb.cfg

  • You can set up additional code trees with separate environment files by changing:

    • archive_jini=f60all_jinit.jar to archive_jini=f60all_jinit.jar,banicons.jar

    • serverURL= to serverURL=/servlet/PPRD

    • form=test.fmx to form=guainit.fmx

    • pageTitle=Oracle Forms Server to pageTitle=Internet Native Banner

    • width=650 to width=800

    • height=500 to height=500

Inb formsweb cfg1
INB – Formsweb.cfg

  • Other changes:

    • separateFrame=false to separateFrame=true

    • background= to background=no

    • lookAndFeel=Oracle to lookAndFeel=Generic

    • archive=f60web.jar to archive=f60web.jar,banicons.jar

    • to,banicons.jar

    • connectMode=socket to connectMode=http

Inb formsweb cfg2
INB – Formsweb.cfg

  • Comment out the following lines:

    • ;serverApp=default

    • ;serverPort=9001

    • ;serverHost=

  • Add:

    • [seed]

    • serverURL=/servlet/SEED

    • [seedsecurity]

    • serverURL=/servlet/SEED

    • form=gsasecr.fmx

Inb jinitiator
INB - Jinitiator

  • Note that Patchset 13 ships Jinitiator version

  • If you do plan on using Jinitiator version, then the following lines in formsweb.cfg need to be appropriately edited for your version of Jinitiator.

    • object_classid=clsid:CAFECAFE-0013-0001-0009-ABCDEFABCDEF

    • object_executable=jinit.exe#Version=1,3,1,9

    • mimetype=application/x-jinit-applet;version=

  • Other Jinitiator versions can be freely downloaded after creating a free OTN (Oracle Technology Network) account from


Inb base htm baseie htm
INB – base.htm, baseie.htm

  • Edit each of the these files

  • Base.htm, baseie.htm:

    • Two (2) lines were added to the file:

      • <PARAM NAME="imageBase" VALUE="%imageBase%">

      • <PARAM NAME="clientDPI" VALUE="%clientDPI%">

    • Three (3) lines are commented out:

      • ;<PARAM NAME="serverPort" VALUE="%serverPort%">

      • ;<PARAM NAME="serverHost" VALUE="%serverHost%">

      • ;<PARAM NAME="serverApp" VALUE="%serverApp%">

Inb basejini htm
INB – basejini.htm

  • Modify this file with:

    • <PARAM NAME="imageBase" VALUE="%imageBase%"> and imageBase="%imageBase%"

    • <PARAM NAME="clientDPI" VALUE="%clientDPI%"> and

    • clientDPI="%clientDPI%"

    • Six (6) lines are commented out:

      • ;<PARAM NAME="serverPort" VALUE="%serverPort%">

      • ;<PARAM NAME="serverHost" VALUE="%serverHost%">

      • ;<PARAM NAME="serverApp" VALUE="%serverApp%">

      • ;serverPort="%serverPort%"

      • ;serverHost="%serverHost%"

      • ;serverApp="%serverApp%"

Inb servlets environments
INB – Servlets environments

  • Copy D:\oracle\806\forms60\server\default.env to D:\oracle\806\forms60\server\ban5.env

  • Add the following lines

    • LOCAL=SID_ban

    • TNS_ADMIN=D:\oracle\806\net80\admin

  • Change the following lines for your environment

    • FORMS60_PATH=D:\sct\SID\fmx

    • REPORTS60_PATH=D:\sct\SID\fmx

    • PRINTER=sctmtal5

    • GRAPHICS60_PATH=D:\sct\SID\fmx

Inb 6iserver conf
INB – 6iserver.conf

  • Stop the OracleHTTPServer service in the Control Panel.

  • Edit the D:\oracle\806\conf\6iserver.conf to add a virtual directory for the Banner help files and to rewrite the url.

    • Alias /hlp/ "D:\sct\inb\SEED\doc\hlp\“

    • Alias /bookshelf/ “D:\sct\inb\SEED\doc\pdf\

Inb dad

  • GJIREVO requires a DAD (Database Access Descriptor).

  • To create a DAD edit D:\oracle\102\Apache\modplsql\cfg\ change:

    • ;admindad = portal30

    • Run gateway.htm: http://host:port/pls/admin_/gateway.htm

      • DAD Name: SID

      • Schema Name: www_user

      • Oracle User Name: www_user

      • Oracle Password: u_pick_it

      • Oracle Connect String: SID_ban

Inb gif files
INB – gif files

  • On your database server or your forms server change directory to the location of your gif files

  • Execute the jar (Java archive tool) command

    • jar cvf banicons.jar *.gif

  • Copy or binary ftp the banicons.jar file to D:\Oracle\Forms60\java

Inb files in general extras upgrade
INB – Files in general/extras (upgrade)

  • fmrpcweb.res (copy or ascii ftp to D:\Oracle\806\Forms60 and rename to fmrweb.res)

    • For F1 display help add this line to fmrweb.res

    • 112 : 0 : "F1" : 1004 : "Help (Item Properties)"

  • cgicmd.dat (copy or ascii ftp to the D:\Oracle\806\Report60\Server).

    • Edit the cgicmd.dat file appropriately as documented in the file cgicmd.dat.

Starting inb nt win2000
Starting INB – NT/Win2000

  • Click on Start -> Settings -> Control Panel -> Services

    • Stop/Start the OracleHTTPServer service.

    • Stop/Start the OracleReportServer service.

  • Execute INB (Internet Native Banner)

  • Start your browser with the URL (example only):


  • When the guainit form starts, enter

    • Username: saisusr

    • Password: u_pick_it

Starting inb unix
Starting INB - UNIX

  • Log on as Oracle

  • . Oraenv (set ias ORACLE_HOME)

  • cd $ORACLE_HOME/Apache/Apache/bin

  • ./apachectl start

  • Start a web browser and enter your url:


Exercise 9
Exercise 9

  • What is the major difference between base.htm, baseie.htm or basejini.htm?

  • You just installed a new patch to Forms – what do you need to change for a new version of jinitiator?

End of session
End of Session

Any Questions?