Ellucian Solution Manager at UNM June 9, 2016 John Lopez, Glenn Nicol

Overview Banner Overview Banner Under the Hood What is ESM? Current Banner Upgrade Process Banner Upgrade Process with ESM Walk through ESM Q & A

Banner Overview Banner is the Enterprise Resource Planning (ERP) software used at UNM Banner is the Ellucian’s higher education ERP solution Interconnected system that manages the university Student Admissions Student Registration and Course Scheduling Financial Aid Finance Human Resources and Benefits Payroll Accounts Receivable Purchasing Salary Planning and Budget Banner XE provides “next generation” of Banner

Banner Under the Hood Each functional area has a related Banner module Each Banner module functions as piece of software with specific version number, a road map for future changes and a set of bugs/changes that need to be resolved Module Examples Banner Student and Student Self Service Banner Financial Aid Banner Employee and Employee Self Service Banner Human Resources Payroll Banner Finance and Finance Self Service Banner Document Management Suite (BDMS) (technical) Banner Workflow (technical) Banner General Person (technical)

Banner Under the Hood Each module periodically requires an upgrade Reasons for upgrades Regulatory change Bug fix Enhancement/new functionality Actual upgrades are a set of files to install PL/SQL Pro C Java Table scripts (straight SQL) Cobol Oracle Form or Report files Shell scripts (UNIX) Upgrades can happen monthly to annually or longer

Banner Under the Hood Upgrades require a village IT Applications Team (Student or Business) IT Platforms DBAs Functional Customers End users Banner Operations cross campus team IT Change Advisory Board (CAB) Ellucian support and advice UNM customizations require modifications to “Banner Delivered” scripts Modifications require a specific process during upgrades Banner versions Current version is Banner 8 Banner XE will begin version 9

Banner Under the Hood Dependencies are not insignificant Example Banner XE Position Description module (required for TMS project) Position Control 8.12.2 module Banner Document Management Suite (BDMS) 8.6 Web xTender upgrade (Ellucian integration partner) Finance 8.10.1 module Web Tailor Employee Self Service General 8.8.2 module Common database upgrade 9.4 Dependencies also change regularly

What is ESM? Ellucian Solution Manager is a software system that provides a centralized, consistent methodology that you can use to download, install, configure, and manage Ellucian products. From the “ESM 1.1. README”

What is ESM? The Ellucian Solution Manager 1.1 release can be used to: Provision Banner environments Download Banner upgrades View documentation for downloaded Banner upgrades View installed product versions and available upgrade releases in Banner environments Install available Banner upgrade releases on both provisioned and existing Banner environments Deploy Banner 8 and 9 online help and Banner 9 applications delivered in Banner upgrade releases to WebLogic servers From the “ESM 1.1. README”

What is ESM? From St. Catherine University: ESM uses Jenkins Does not manage “solutions” Does not manage all Ellucian products Does manage upgrades of Banner products Banner Upgrade Manager (BUM) may be a more appropriate name ESM uses Jenkins Wikipedia: Jenkins is an open source continuous integration tool written in Java. St. Catherine University: A Jenkins master process runs on the ESM server, and Jenkins slave agents run continuously on the job submission, INB, SSB, and XE application servers. Transformed forms required ESM, made it a priority

Current Banner Upgrade - Preparation Preparatory Work Identify need for upgrade Bring scheduling recommendations from core offices to Banner Operations Banner Operations schedules release dates for each instance around operational calendar Create a Change Request and Release records with the IT CAB Add scheduled upgrade date to DBA and ERP calendars Investigate Dependencies Check Ellucian dependency matrix Review upgrade documentation Create case with Ellucian to verify identified dependencies

Current Banner Upgrade - Preparation Investigate Modifications Download documentation from Ellucian site Review documented objects being upgraded Review upgrade scripts and identify objects being upgraded Augment final object list Identify objects containing UNM modifications Retrofit UNM modifications into upgraded objects Review upgrade with customers Recommend and request from Banner Operations approval of Upgrades to the first environments - BANSEED and then BAND by the dba group.

Current Banner Upgrade – Installation Phase 1 DBA Pre-Upgrade Steps Done manually before the day of the upgrade upon request of developers Download upgrade files and move to appropriate BANNER TREE for each instance Apply to BANSEED (Vanilla Banner Environment) A.S.A.P no scheduling needed. On application to BANSEED develop an upgrade sequence list of steps in BAND from the supplied upgrade guide. We add UNM specific steps and UNM default upgrade passwords.

Current Banner Upgrade – Installation Phase 2 DBA Preparation of the environment on day of upgrade Run Backups Stop AppWorx trains Stop processes Stop Banner Workflow Put database in restricted mode Grant restricted access to necessary id’s Change passwords to all schemas for the duration of the upgrade.

Current Banner Upgrade – Installation Phase 3 DBA Manual install of Banner module(s) upgrade Module_ready.sql script (checks prerequisites) Import into the databases (importing new changes for tables into db) guovmods.sql (giving upgrade owner privilege to do upgrade) Pre-Upgrade compile (to verify objects before upgrade) Gostage.sql (applies all the changes using scripts for each mod to the imported objects) module_migration_script (this moves scripts that were run to the banner home directory for the environment & creates links to the BANNER_LINKS directory) Compiles - C, cobol, java, and banner forms Verify the state of the upgraded environment: gurscls, rudone.sql, modudv(update version)

Current Banner Upgrade – Installation Phase 4 Manual run of Post Upgrade Steps, clean up tasks and testing. Restart Services Restart Processes Recompile special forms Restart AppWorx trains Restart Banner Workflow Check services are running Change Passwords back to normal. Take the database out of restricted mode Take a backup Do initial testing of objects ie Banner forms Notify Developers Add UNM modifications to updated objects if any

Current Banner Upgrade – Conclusion Test installation in Production Work with core offices on day of upgrade Test relevant areas in Banner based on upgraded modules Upgrade is signed off Complete documentation of upgrade Update Banner version in CMDB Complete documentation in Knowledge Management system Hand off to support Meet with ERP Application Support team to review changes in the upgraded modules Meet with Service Desk if necessary

Current Banner Upgrade Process Preparation Seed BAND BANI BANP Conclusion Preparatory Work Prepare for upgrade Prepare for upgrade Prepare for upgrade Prepare for upgrade Test installation Investigate Dependencies Perform upgrade Perform upgrade Perform upgrade Perform upgrade Complete Documentation Investigate Modifications Restart objects after upgrade Restart objects after upgrade Restart objects after upgrade Restart objects after upgrade Hand off to Support Review with customer Add UNM modifications Add UNM modifications Add UNM modifications

Proposed Banner Upgrade Process Preparation Seed BAND BANI BANP Conclusion Preparatory Work ESM ESM ESM ESM Test installation ESM ESM ESM ESM ESM Complete Documentation Investigate Modifications ESM ESM ESM ESM Hand off to Support Review with customer Add UNM modifications Add UNM modifications Add UNM modifications

What does ESM do ? Configure existing and install new banner environments Development, Integration, Production, Sandbox, Training Download upgrade files & documents for dependencies management (Assists with Preparation tasks for Developers & DBA’s Phase 1) Manage Ellucian products (General, Student, Finance, etc) Dependencies Prepping for the upgrade Performing the upgrade(s) Post-upgrade tasks Phases 2-4 The upgrade - done via the BMUI which stands for Banner Multi-upgrade User Interface. It is the upgrade component of ESM. It recognizes repeatable steps in upgrades and runs upgrades just as the DBA group would do.

Current Upgrade Process BMUI Solution Manager Process Phase I - Upon request of developers manual run of Pre Upgrade Steps Download of upgrade files from ellucian apply to SEED. Phase II - Preupgrade Prepare environment for upgrade Phase III - Manual run of Banner module(s) upgrade MODULE_ready.sql script (checks prerequisites) import into the databases (importing new changes for tables into db) guovmods.sql (giving upgrade owner privilege to do upgrade) Preupgrade compile (to verify objects before upgrade) Gostage.sql (applies all the changes using scripts for each mod to the imported objects) module_migration_script (this moves the scripts that were run to the banner home directory for the environment and creates links to the BANNER_LINKS directory) compiles- C, cobol, java, and banner forms Verify the state of the upgraded environment: gurscls, rudone.sql, modudv(update version) Phase IV - Manual run of Post Upgrade Steps

A Walk through ESM Environment Browser window or screen shots if not working Need to put order HERE

A Walk through ESM Environment Browser window or screen shots if not working Need to put order HERE

A Walk through ESM Environment Browser window or screen shots if not working Need to put order HERE

A Walk through ESM Environment environment BANSANDBOX Browser window or screen shots if not working Need to put order HERE

A Walk through ESM Environment Demo for Proof of Concept Environment BANSANDBOX Products Tab Upgrades Tab Deployments Tab Links Tab Env setting Tab Applications tab App Servers Tab Machines Tab Credentials Tab Browser window or screen shots if not working Need to put order HERE

Banner Upgrade Process with ESM Manual PREP work is automated downloads Both Documentation and upgrade files Figuring-out dependencies I would say here trust but verify.

Q & A Questions? Thoughts? Excited?

Ellucian Solution Manager at UNM Thank you!