1. Technical Changes for Third-Party Banner Users March 27, 2006 9-11 a.m. MU II, Memorial Union

2. Presenters Application Development and Data Administration - IET Peter Brinckerhoff, Banner Project Manager (pjbrinckerhoff@ucdavis.edu) Jamila Sahakian, Banner System Architect (jpsahakian@ucdavis.edu) Data Center and Client Services - IET Patrick Kelly, Data Resource Manager (pjkelly@ucdavis.edu) Office of the Vice Provost – IET Robert Ono, IT Security Coordinator (raono@ucdavis.edu) Leng Thao, Programmer (ljthao@ucdavis.edu)

3. Overview The new version of Banner will be implemented September 2-4, 2006. Todays 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.

4. Application Highlights Jamila Sahakian Banner user interface

5. Banner 6

6. Banner 7

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 clients computer.

8. Application Highlights Jamila Sahakian Banner user interface Application Programming Interfaces (APIs)

9. 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.

10. Application Highlights Jamila Sahakian Banner user interface Application Programming Interfaces (APIs) Authentication

14. Application Highlights Jamila Sahakian Banner user interface Application Programming Interfaces (APIs) Authentication Centralized Matching Process

15. Application Highlights Jamila Sahakian Banner user interface Application Programming Interfaces (APIs) Authentication Centralized Matching Process Fine-Grained Access

16. Technical Changes Jamila Sahakian Tables – new and dropped

17. Tables – New and Dropped Tables – NewChangeImpact 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 rows 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)ChangeImpact GORFLTRGraphic-related table removedNo impact GORGCATGraphic-related table removedNo impact GORGROPGraphic-related table removedNo impact GORGRPHGraphic-related table removedNo impact GORGSAVGraphic-related table removedNo impact GORSLCTGraphic-related table removedNo impact RERSTIDThe table was dropped and recreated for an enhancement as part of Common Origination and Disbursement project No impact RCTXMLDThe table was dropped and recreated for enhancements as part of Common Origination and Disbursement project. No impact TTBTAXITSATAXI form is obsolete.Remove any code references to this table

18. 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). Concurrent Curricula Phase I – Functional Process Flow

19. Technical Changes Jamila Sahakian Tables – new and dropped Columns – changed and dropped

20. Columns – Changed and Dropped ColumnsChanges (Not Null Columns) Added to TablesImpact GUBINST_ONLINE_MATCH_INDGUBINSTNo impact GURMESG_VPD_INDGURMESGNo impact TWGBWMNU_ADM_ACCESS_INDTWGBWMNUNo impact TWGBWRUL_CGIBIN_DIR_ADMTWGBWRULNo impact Columns – Dropped (Obsolete)ChangeImpact RPRADSB_ACPT_DISB_NEG_PEND _AMT Column dropped from RPRADSB tableRemove any code references to this column ZORDEPT_EMPLOYEE_IDColumn dropped from ZORDEPTRemove any code references to this column

21. Technical Changes Jamila Sahakian Tables – new and dropped Columns – changed and dropped Views – dropped

22. Views – Dropped Views – Dropped (Obsolete)ChangeImpact GOVGMSK Replaced by fine-grained accessNo impact GOVVMAC Replaced by fine-grained accessNo impact GOVVRAC Replaced by fine-grained accessNo impact

23. Technical Changes Jamila Sahakian Tables – new and dropped Columns – changed and dropped Views – dropped Analyzing code for changes to database objects

24. Changes for Current Banner 6 Jamila Sahakian Code changes for College of Biological Sciences

25. Account Management Changes Patrick Kelly Cyber-safety compliance (http://security.ucdavis.edu)

26. Account Management Changes Patrick Kelly Cyber-safety compliance (http://security.ucdavis.edu) Types of accounts

27. Departmental or personal accounts Application accountsUser 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

28. Account Management Changes Patrick Kelly Cyber-safety compliance (http://security.ucdavis.edu) Application accounts vs. user accounts Mothra entries

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

30. Account Management Changes Patrick Kelly 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

31. Account Management Changes Patrick Kelly 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

32. Reporting Tools Jamila Sahakian and Leng Thao Account consolidation

33. Account Changes Group 1: Departmental or personal accountsChange 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 accountsChange 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 accountChange 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.

34. Reporting Tools Jamila Sahakian and Leng Thao Account consolidation Third-party tools, Advanced Security Option (ASO) and hard token

35. Reporting Tools Jamila Sahakian and Leng Thao Account consolidation Third-party tools, Advanced Security Option (ASO) and hard token Open Database Connectivity (ODBC) driver

36. Reporting Tools Jamila Sahakian and Leng Thao Account consolidation Third-party tools, Advanced Security Option (ASO) and hard token Open Database Connectivity (ODBC) driver Oracle 10g client

37. Project Timeline Peter Brinckerhoff Testing for third-party users

38. Group 1: Users who have a departmental or personal account and Banner hard token account. DateWhoTask March 27Banner TeamAssign third-party role to Banner hard token account on TESTx. March 27– June 1 Third-party usersTest 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 desktop@ucdavis.edu. Recharge rates for services will apply. Note: Macintosh users send email to banner-help-desk@ucdavis.edu for more information. By June 1Third-party usersSend tool testing results to banner-help-desk@ucdavis.edu Note: If your testing is successful, you will use your Banner hard token account after the Banner 7 upgrade. By August 15Banner TeamReview 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 4Third-party usersConfigure tools to connect to Production database. By October 3Third-party usersMust use Banner hard token account with third-party tool. October 3Banner TeamOld third-party account will be locked. October 3Third-party usersContact 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

39. Group 2: Users who have an application account. DateWhoTask May 17Banner TeamImplements 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 22Third-party usersChange password. No warnings will be received during the 35-day grace period. Password will expire June 22, 2006. June 22Third-party usersPassword will expire June 22, 2006. Group 2 Timeline

40. Group 3: Users who have departmental or personal accounts but no Banner hard token account. DateWhoTask March 27–May 1Third-party usersEmail tool and version information to banner-help-desk@ucdavis.edu for assistance. June 1Banner TeamFollow-up with Group 3 on information for reporting tools and the need for a hard token. Group 3 Timeline

41. Project Timeline Peter Brinckerhoff Testing for third-party users Implementation schedule for Banner 7

42. Banner 7 Upgrade DateWhoTask Sept 2–4 (Labor Day weekend) Banner TeamUpgrade weekendBanner unavailable. Banner Upgrade

43. 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 banner-help-desk@ucdavis.edu 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 banner-help-desk@ucdavis.edu 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.

44. Other Resources Peter 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: banner-help-desk@ucdavis.edu

45. Meeting Evaluation and Tool Survey Peter Brinckerhoff We appreciate your feedback! Please complete the meeting evaluation and tool survey. Thank You!

46. Questions and Answers