technical changes for third-party banner users march 27, 2006 9-11 a.m. mu ii, memorial union

Technical Changes for

Third-Party Banner Users

March 27, 2006

9-11 a.m.

MU II, Memorial Union

Presenters

Application Development and Data Administration - IET

Peter Brinckerhoff, Banner Project Manager ([email protected])

Jamila Sahakian, Banner System Architect ([email protected])

Data Center and Client Services - IETPatrick Kelly, Data Resource Manager ([email protected])

Office of the Vice Provost – IETRobert Ono, IT Security Coordinator ([email protected])

Leng Thao, Programmer ([email protected])

Overview

• The new version of Banner will be implemented September 2-4, 2006.

Today’s presentation:

• Presents important technical changes that will impact third-party Banner users.

• Provides detailed information about steps departments will need to take prior to the Banner 7 upgrade.

Application Highlights Jamila Sahakian

• Banner user interface

Banner 6

Application Highlights – Banner User Interface

Banner 7


Banner 7 Features


• New screen resolution size of 1024 by 768. Note: Most 15-inch and some 17-inch monitors do not support this large screen size.

• Banner 7 forms will be accessed via a Web browser.

• Windows-looking screens have navigational tabs and more legible text.

• Supported Web browsers: Microsoft Internet Explorer 6 Mozilla Firefox 1.0 (Windows only) Safari 1.2 (Macintosh)

• Banner 7 will also require the download of a plug-in, JInitiator The plug-in is used to run Java applets on the client’s computer.


Banner user interface

• Application Programming Interfaces (APIs)

Application Highlights – Application Programming Interfaces (APIs)

The business logic from Banner forms, Web pages, and processes have been migrated into common procedures and stored in the database to create Application Programming Interfaces (APIs). APIs provide the following:

Support for common create/retrieve/update/delete commands. Validation of business rules for the underlying entity or table. Can be used by internal Banner programs as well as by external systems integrating to Banner.


Banner user interface Application Programming Interfaces (APIs)

• Authentication

Application Highlights - Authentication


RAIDUS authentication for third-party tool to access the Banner database 1. User enters database account and hard token (one-time) password to

Banner (Oracle) database. 2. Banner database passes data to the RADIUS client. 3. RADIUS passes the data to Safeword. 4. The authentication server passes an accept or reject status to the

RADIUS server. 5. RADIUS server passes the authentication to Banner. 6. User connects to the Banner database via third-party tool.

Banner database

User

Radius Safeword

21 3

45

User enters database account and hard token (one-time) password

Authentication

User connects to the Banner database via third-party tool

6


Authentication for an application account and an assigned password to access the Banner database 1. Using an application account and assigned password for the Banner

(Oracle) database; the third-party tool connects to the Banner database.

Banner database

End User

1Using application account

and assigned password; the third-party tool connects to the Banner database


Banner user interface Application Programming Interfaces (APIs) Authentication

• Centralized Matching Process


Banner user interface Application Programming Interfaces (APIs) Authentication Centralized Matching Process

• Fine-Grained Access

Technical Changes Jamila Sahakian

• Tables – new and dropped

Tables – New and Dropped

Tables – New Change Impact

SORLCUR SORLFOS

Allow for the storage of an unlimited quantity of curriculum data. The SORLCUR table stores the curriculum data (i.e., program, level, college, campus, and degree), while the SORLFOS table stores the majors, minors, and concentrations. Each entry in both the SORLCUR and SORLFOS tables has a unique one-up sequence number. This sequence number allows each row to be distinct. In addition, the rows in the SORLFOS table are linked to their corresponding SORLCUR table entries by the SORLCUR row’s sequence number. The module code (RECRUIT, ADMISSIONS, etc.) and key sequence number associated with each SORLFOS field of study row are derived from the SORLCUR row to which they are linked.

Affected tables are: SRBRECR, SARADAP, SGBSTDN and SHRDGMR. The data will be back filled into these tables from SORLCUR and SORLFOS through the next version of Banner (Banner 8). See data map below.

Tables – Dropped (Obsolete) Change Impact

GORFLTR Graphic-related table removed No impact

GORGCAT Graphic-related table removed No impact

GORGROP Graphic-related table removed No impact

GORGRPH Graphic-related table removed No impact

GORGSAV Graphic-related table removed No impact

GORSLCT Graphic-related table removed No impact

RERSTID The table was dropped and recreated for an enhancement as part of Common Origination and Disbursement project

No impact

RCTXMLD The table was dropped and recreated for enhancements as part of Common Origination and Disbursement project.

No impact

TTBTAXI TSATAXI form is obsolete. Remove any code references to this table

Technical Changes

RecruitGeneral Rec/Recr infoTermCurriculum 1

AdmissionsGeneral Rec/Adm infoTerm and Appl NumberCurriculum 1Curriculum 2

General StudentGeneral Student infoSequence NumberEffective TermCurriculum 1Curriculum 2

Academic HistoryAcademic History infoDegree Sequence NumberTermCurriculum 1Curriculum 2

SRARECRSRBRECR, SRRCHRT,SRRCMNT, SRRRSRC,SRRLCUR

SAAADMSSARADAP, SARSRCE,SARCHRT, SARCMNT,SARLCUR, SARQUAN,SARCHKL

SGASTDNSGRSRCE, SGRCHRT,SGRCMNT, SGRLCUR

SFAREGSSFRSTCR, SFRAREG

SHADEGRSHRDGMR, SHRTRAN,SHRLCUR

SOAOLIB-SOALCURSORLCUR, SORLFOS

Adm Source InfoAdm CohortAdm CommentsAdm Quest & AnswAdm Checklist

Recruit Source InfoRecruit CohortRecruit Comments

Gen Stu Source InfoGen Stu CohortGen Stu Comments

RegistrationTerm, Status

CRN, Status, Term

Academic HistoryTerm, Status

Academic History CoursesTerm, Course

Curriculum Base(SORLCUR)

Curriculum Field of Study

(SORLFOS)

7.0 Bridge

7.0 Bridge

7.0 Bridge

7.0 Bridge

Data Map Forms

SunGard SCT will support the backfill of data to the current tables (SRARECR, SAAADMS, SGASTDN, SFAREGS, SHADEGR) for one year. Another update will be provided in approximately six months on the plans for fully implementing the new base tables for Concurrent Curricula (SORLCUR and SORLFOS).

Technical Changes

Concurrent Curricula Phase I – Functional Process Flow


Tables – new and dropped

• Columns – changed and dropped

Columns – Changed and Dropped

Columns—Changes (Not Null Columns)

Added to Tables Impact

GUBINST_ONLINE_MATCH_IND GUBINST No impact

GURMESG_VPD_IND GURMESG No impact

TWGBWMNU_ADM_ACCESS_IND TWGBWMNU No impact

TWGBWRUL_CGIBIN_DIR_ADM TWGBWRUL No impact

Columns – Dropped (Obsolete) Change Impact

RPRADSB_ACPT_DISB_NEG_PEND_AMT

Column dropped from RPRADSB table Remove any code references to this column

ZORDEPT_EMPLOYEE_ID Column dropped from ZORDEPT Remove any code references to this column

Technical Changes


Tables – new and dropped Columns – changed and dropped

• Views – dropped

Views – Dropped

Views – Dropped (Obsolete) Change Impact

GOVGMSK Replaced by fine-grained access No impact

GOVVMAC Replaced by fine-grained access No impact

GOVVRAC Replaced by fine-grained access No impact

Technical Changes


Tables – new and dropped Columns – changed and dropped Views – dropped

• Analyzing code for changes to database objects

Changes for Current Banner 6Jamila Sahakian

• Code changes for College of Biological Sciences

Account Management Changes Patrick Kelly

• Cyber-safety compliance (http://security.ucdavis.edu)


Cyber-safety compliance (http://security.ucdavis.edu)

• Types of accounts

Account Management Changes

Departmental or personalaccounts

Application accounts User accounts (or Banner hard token account)

Accounts connect to the Banner database with an assigned password via third-party tools. Departmental accounts are shared by users within the same department. Personal accounts are assigned to an individual.

Accounts used in a locally developed application. Accounts connect to the Banner database with an assigned password via the server running the application. Example: MyUCDavis or Financial Aid's EFAN application.

These are personal accounts for accessing Banner forms using a hard token (one-time) password.

Types of Accounts


Cyber-safety compliance (http://security.ucdavis.edu) Application accounts vs. user accounts

• Mothra entries


Cyber-safety compliance (http://security.ucdavis.edu) Application accounts vs. user accounts Mothra entries

• Password management to be implemented in Banner 6


Cyber-safety compliance (http://security.ucdavis.edu) Application accounts vs. user accounts Mothra entries Password management to be implemented in Banner 6

• Changing your password


Cyber-safety compliance (http://security.ucdavis.edu) Application accounts vs. user accounts Mothra entries Password management to be implemented in Banner 6 Changing your password

• Password rules

Reporting ToolsJamila Sahakian and Leng Thao

• Account consolidation

User Accounts and Reporting Tools

Account ChangesGroup 1: Departmental or personal accounts Change for Group 1

Accounts connect to the Banner database with an assigned password via third-party tools. Departmental accounts are shared by users within the same department. Personal accounts are assigned to an individual.

These accounts will need to use a hard token if the third-party tool is RADIUS-compatible.If these account owners have a Banner hard token account, the third-party role will be consolidated with their Banner hard token account. The old third-party account will be locked.

Group 2: Application accounts Change for Group 2

Accounts used in a locally developed application. Accounts connect to the Banner database with an assigned password via the server running the application. Example: MyUCDavis or Financial Aid's EFAN application.

No change. These accounts will continue to have an assigned password. Password management will be applied.

Group 3: Departmental or personal but no Banner hard token account Change for Group 3

Accounts connect to the Banner database with an assigned password via third-party tools; however, the account owner does not have a Banner hard token account and therefore does not have a hard token.

These accounts will need to obtain a hard token if the third-party tool is RADIUS-compatible. Otherwise an assigned password will remain in effect. Password management will be applied.


Account consolidation

• Third-party tools, Advanced Security Option (ASO) and hard token


Account consolidation Third-party tools, Advanced Security Option (ASO) and hard token

• Open Database Connectivity (ODBC) driver


Account consolidation Third-party tools, Advanced Security Option (ASO) and

hard token Open Database Connectivity (ODBC) driver

• Oracle 10g client

Project Timeline Peter Brinckerhoff

• Testing for third-party users

Project Timeline

Group 1: Users who have a departmental or personal account and Banner hard token account.

Date Who Task

March 27 Banner Team Assign third-party role to Banner hard token account on TESTx.

March 27–June 1

Third-party users Test tools on TESTx with Banner hard token account, ODBC, ASO. If you need assistance with the installation of the software components, contact 757-8907 or email [email protected]. Recharge rates for services will apply.Note: Macintosh users send email to [email protected] for more information.

By June 1 Third-party users Send tool testing results to [email protected]: If your testing is successful, you will use your Banner hard token account after the Banner 7 upgrade.

By August 15 Banner Team Review tool testing results. Was tool testing is successful?YES. Consolidate third-party account with Banner hard token account.NO. Third-party account remains and account will be added to the password complexity profile. Important note: You must change your password September 4–October 3. You will receive warnings during the 30-day grace period. Password will expire on October 3.Users will be notified by email to confirm account information.

September 4 Third-party users Configure tools to connect to Production database.

By October 3 Third-party users Must use Banner hard token account with third-party tool.

October 3 Banner Team Old third-party account will be locked.

October 3 Third-party users Contact the Banner Help Desk to have account unlocked. Unlocked account is added to the password complexity profile. Users need to change password. Password will expire on October 3, 2006.

Group 1 Timeline

Project Timeline

Group 2: Users who have an application account.

Date Who Task

May 17 Banner Team Implements password complexity for application accounts, which will continue to use an assigned password. This will be implemented in Banner 6 for the development, testing, and production environments and will stay in effect after the Banner 7 upgrade.

May 17–June 22 Third-party users Change password. No warnings will be received during the 35-day grace period. Password will expire June 22, 2006.

June 22 Third-party users Password will expire June 22, 2006.

Group 2 Timeline

Project Timeline

Group 3: Users who have departmental or personal accounts but no Banner hard token account.

Date Who Task

March 27–May 1 Third-party users Email tool and version information to [email protected] for assistance.

June 1 Banner Team Follow-up with Group 3 on information for reporting tools and the need for a hard token.

Group 3 Timeline

Project Timeline Peter Brinckerhoff

Testing for third-party users

• Implementation schedule for Banner 7

Project Timeline

Banner 7 Upgrade

Date Who Task

Sept 2–4(Labor Day weekend)

Banner Team Upgrade weekend—Banner unavailable.

Banner Upgrade

Conclusion

What To Do

1. Review the table and column changes to see what might affect your local code.

2. Test your third-party tools to see if they are RADIUS-compatible. Send your testing results to [email protected] by June 1, 2006.

3. If you have an application account (see page 11), change your password beginning May 17, 2006. Passwords expire June 22, 2006.

4. If you have a departmental or personal account (see page 11) but no Banner hard token account, email the tool and version information to [email protected] for assistance and additional information by May 1, 2006.

5. Do your final code and tool testing by September 4, 2006.

6. Configure tools to connect to Production database by September 4, 2006.

Other ResourcesPeter Brinckerhoff

• For Banner information, visit http://sis.ucdavis.edu/

• For developer resources, visit http://sis.ucdavis.edu/

and click the Developer Resources link

• Email the Banner Help Desk: [email protected]

Meeting Evaluation and Tool SurveyPeter Brinckerhoff

We appreciate your feedback!Please complete the meeting evaluation

and tool survey.

Thank You!

Questions and Answers

technical changes for third-party banner users march 27, 2006 9-11 a.m. mu ii, memorial union

Documents