Banner XE Update
UNC CAUSE 2013
ITS-Management Information Systems
Banner Administrative Screens
Brief Technology Review
Foundations in Oracle Character Mode Forms
Evolution to “GUI” Fat Client Forms late 1990s.
2004 SCT bought by SunGard
ERP Movement to the Browser...
Oracle Application Server/INB
Adobe Flex for “New Products”
Discussions starting 2008
Something other than Oracle Forms
Java Stack selected 2009 for “Horizon”
Available Banner XE Releases
Banner Catalog (9.1) May 2012
Banner Schedule (9.1) May 2012
Events Management (9.1) August 2012
Attendance Tracking (9.0) August 2012
Faculty Grade Entry (9.1 ) October 2012
Catalog & Schdule (9.2) December 2012
Faculty Grade (9.2) in Development
UNCG Banner XE Project Goal
● Stand up for production use within Registrar’
s Office baseline Banner Student Catalog
and Course Schedule
To do that we needed to figure out a few new
XE eXtensible Ecosystem
Challenges: New Everything
New Fields in the Oracle Database (DBEU)
New Application Servers (Unix to Linux)
New App Server Hardware (Real to VM)
New Source Code Management Model (Git)
New Application Framework (INB to
New Way of Thinking (Object Oriented)
New Developer Tools (Oracle to Java Centric)
New Security Model (Oracle to SSO)
Scope of XE Changes
● More technical change than OS Switch or
Oracle Major Version upgrade.
● Architectural reset to position Banner
products for next 10+ years
● Evolutionary change, but "First Hurdles" are
● Offers architectural choices but with
Open Source vs Commercial Products.
● Once in a Career Change, Don’t
Executed Database Extension Utility (spring
Targeted Hire within MIS to focus on XE
Code camp (1 day)
Java (3 Day)
Groovy Grails (5 Days)
Trial Run (Feb 2013)
Banner XE Extensibility (3 days)
First Use Apps: Batch w/Groovy
Project Development Environment (UGDEV8)
Project Environment (UGVAL7)
Testing/Validation Environment (UGVAL3)
Live in Production (BANPRD) (May 2013)
Benefits of XE
Off of End of Life Oracle Forms.
"Modern Look and Feel"
Separation of presentation from business logic.
Concept of Sub module as tight application vs
collection of forms & processes
Still Much to Do
Continue to Develop Operational Procedures in
MIS & DBA Group.
Load Balancing in support of High Availability
Overcome Authentication Hurdles.
Prepare for additional modules coming soon.
Consolidation of code into more API's
Logic in one place for use in Admin, Self
Service, Batch, Web Services, etc.
Should reduce scenarios data in anomalous
forms gets past one process but then chokes
Test Driven Development Model
● Automated Test Plans to "exercise" code for
basic input/output scenarios, issues
● Speeds run throughs to catch dumb
● Will still require end user testing, but on
more navigation than on basics.
● Still have to author "testing code"
● Layers of Testing: Grails Test Units +
Selenium UI Testing Managed by JENKINS
UNCG must develop Single Sign On
Framework for Banner tools.
Likely Shibboleth centric for UNCG (have not
done CAS at UNCG)
Single Sign On framework must become High
Potentially extensible to other applications.
XE Administrative (INB equivalent) and XE
Self Service (UNCGenie equivalent)
technical platforms will likely become more
similar than todays INB & SSB.
More similar user experience
More similar programming environments (Still
Speed of availability for INB Replacements.
Ellucian Roadmaps do not yet lay out target
end times for full conversion of major modules.
During interim ITS will have to maintain old and
new skill sets, hardware & maintenance effort
MTS estimate 4+ years to make transition.
Users operating in "Mixed Mode" (Old INB &
New XE) based on which submodules they
Keyboard Shortcuts vary
Ctrl-Page Down vs "Go"
Roll Back vs "Start Over"
Critical to get authentication working before
Will require recoding of
UNCG Baseline Mods (35 ish)
UNCG Custom Programs (100+)
GA/Alliance Custom/Mods (???)
New framework has potential to manage our
local mods differently
Developer desktop Java management
challenges will persist. (But end user Java
issues are removed for XE apps vs INB)
MIS developers must learn multiple tools to
effectively author Java code in an Ellucian