IT Briefing September 2006
IT Briefing Agenda 9/21/06 • SWE Updates • Karen Jenkins • Manage IT Upgrade • Karen Jenkins • Blackboard Overview • Sandra Butler • Web Approach • Karen Jenkins • Net. Com Q&A • Paul Petersen October 19 Briefing 10: 15 – 1: 30 – MS to attend: • 1 hour for Product Roadmap • 1 hour for Vista and Office 2007 MS to provide lunch. Please RSVP to: sebreana. williams@emory. edu 1
Software Express • Microsoft access – Student employees no longer given access • Sponsored accounts & retirees – No longer given access • Examining all applications against our contracts and will make adjustments accordingly • Any issues? 2
Manage IT Karen Jenkins Andrew Kincaid Al Shelton
Remedy Modules Service Desk Change Management Action Request System Service Level Management Asset Management 4
Architecture 5
Remedy Upgrade – Heads up! • • • Major new release v 7. 0 More ITIL compliance Multi-tenancy Additional categorization – from 3 levels to 6/7 (product & operational) Cleaner look – left navigation & top navigation Solutions/knowledgebase – added user flag Definitive Software Library (DSL) CMDB – with new tools to assist the build, graphical view REMOVED the “teaser” apps 6
Service Desk (Help Form) • New name for Help Desk module • Largest graphical change is top ITIL process bar • 2 types of Requests (ITIL compliance) – Incident – Problem • Task management added (use with incidents, problems, or change requests) • New canned reports • Enhanced problem management, new form • Work log renamed to Work Info (table based) • Other fields renamed (such as severity to impact) • Decision tree and scripts 7
8
9
Change Management • Module now required to create any type of change request • More/tighter integration with Configuration Management, DSL, & CMDB – Closed loop change • Change calendar w/ business events • Set varying approval levels – even autoapprove – so process is not bogged down • Save high risk changes for CAB 10
11
Other Applications • Service Level Management – Ability to compute overall SLA compliance with multiple weighted targets – Performance targets via SNMP interface (SMARTS) • Asset Management – Better integration with Configuration Management (aka Marimba) – DSL contains a product dictionary – Software license management 12
Input & Schedule • First Tech. Talk tomorrow 2: 00 -3: 30 NDB 225 Kennesaw – 10/13, 11/24 • Will also updates at IT Briefing • Target installation => October • Go-live => TBD • Initial scope = migrate current functionality & data 13
Manage IT ? Questions 14
Blackboard @Emory Sandra Butler Manager, Interactive Technologies Team IT Briefing 09/21/06
Interactive Technologies Team • Adam Lipkin • Marcy Alexander • Tricia Goddard • Kathy Hayes • David Lower • Julia Leon • Marianne Schneider • Open Slot 16
Interactive Technologies • Learn. Link • Blackboard – classes. emory. edu – classes@emory. edu • Insight • Wimba 17
What is Blackboard (Bb)? • Academic Suite – Learning System – Community System – Content System • Building Blocks – Add-ins that extend capability and functionality 18
Bb Tools • Course and Content Authoring • Assessment Engine • Assignment Manager • Online Gradebook • Discussion Board • • Email Class Virtual Chat Group Management Course Reporting and Statistics • Performance Dashboard/Review Status (recent upgrade) more available via Building Blocks and Course Cartridges 19
History: Bb at Emory 1999: review Bb Course. Info versus Web. CT teaching & learning at anytime from anywhere 2000: University adopts Bb 5; upgrade to Course & Portal Manager depts, orgs, and clubs; customizable buttons; building blocks announcement (Bb Inc. ) 2002: upgrade to Bb 5. 5 Enterprise Bb app server & Oracle db server; move to 24/7 data center; custom script for enrollment; Emory’s Gen. Lib developers release e-reserves interface for Bb; branding 2004: upgrade to Bb 6. 1 LDAP enabled; PS feeds via Bb snapshot utility; dual servers in PROD and DEV 20
History: Bb at Emory 2005: license Content System; SSL & load balanced; upgrade to Bb 6. 2 file mgmt; content sharing; e. Portfolios; passes to entire community and guests; Wimba Building Block trial 2006: Reorganize / AAIT / ATS / Interactive Technologies app system support transition; upgrade to Bb 6. 3; RSPH migrates to University Bb servers; add’l training and outreach (ex. JIT sessions, custom training sites, etc. ); increased non-academic and training usage; Wimba Building Block added 2007: Enhance integration w/other IT resources review overall structure: enhance processes; improve infrastructure 21
Bb at Emory Stats 09/18/06 2: 00 pm • 3, 255 courses – 1, 772 active courses (08/06 – current) • 163 organizations – 104 active organizations (08/06 – current) – includes intranets, student forums and groups, faculty/staff groups and committees 22
Bb at Emory Stats 09/18/06 2: 00 pm 23
Bb Course Site 24
Building Block: Wimba Voice Tools 25
26
Bb & Insight integration made easy 27
https: //classes. emory. edu 28
Proposed Web Approach September 2006
Agenda • Current environment • Initial plan • Revised plan • Architecture goals • Draft architecture • Estimated timeline • Outstanding issues 30
Gecko & Maple • Focused on the needs of the hard core developer community • Maple Issues: – Difficult to support & maintain due to multiple customizations (Apache, “ITD Web. Drive”) – Security issues – Old hardware 31
Initial Plan • Update hardware • Update software ? But what are the most common needs of the community ? Does this hit the mark … Stabilize, re-group, gather requirements 32
Stabilize • Split Site. Minder / non-Site. Minder sites – Solved the performance issues identified in March ‘ 06 • Upgrade CF to 7. 1 (Maple) – Containment capabilities improve stability – Majority of code in CF – allowed for early testing prior to new architecture • Identify high risk security issues – Plan in place to implement changes 33
Community Requirements • Developers only need a couple of additional features: – My. SQL, shell access on Dev, stability • Resource and/or skill set constrained users are the majority – Analysis indicates there are many static sites and others with basic/common minor dynamic components (~77%) • One size does not fit all … 34
Revised Plan • Place focus on the majority and the current gaps • Build a tiered service offering – target different customers/needs • Build tool kit for common needs • Provide more applications • Improve documentation 35
Web Approach Tiered service offerings dependant upon user needs • Standard Hosting – Users with limited resources needing to quickly and easily publish static websites • Advanced Hosting – Users with advanced developments skills creating dynamic sites and/or web applications • Enterprise Hosting – Users creating mission critical enterprise websites and/or enterprise web applications 36
FUTURE STATE
Hosting Options Service & Support Standard Advanced Enterprise Backup/Restore Server maint. Proactive Monitoring System admin. High avail. Web Workshops Assigned POC 38
Hosting Options (cont. ) Features & Tools Standard Advanced Enterprise Templates Site builder Script library Site statistics Google search Error/log files Virtual servers 39
Hosting Options (cont. ) Features & Tools (continued) Standard Advanced Enterprise 500 MB 1 GB 2 GB s. FTP File Manager SSH (dev) Cronjobs Dev/QA Env. Dev-to-prod Disk space 40
Hosting Options (cont. ) Site & Application Development Standard Advanced Enterprise HTML PHP 4. 3. 2 Cold Fusion 7. 1 Perl 5. 8 Python 2. 3 J 2 EE Site. Minder 41
Hosting Options (cont. ) Database Development Standard Advanced Enterprise Oracle My. SQL Cold Fusion Connectors Oracle My. SQL Microsoft SQL RAC JDBC 42
Hosting Options (cont. ) Applications Standard Advanced Enterprise Blog Calendar Message Board CMS Portal 43
Architecture --DRAFT--
Architecture Goals • Low entry-barrier • Consolidate where possible • Improved isolation / management • Seamless scalability • Highly secure • High stability, availability, and performance 45
46
47
Project Scope Phase 1 and beyond
Project Scope • Design & implement new robust web infrastructure • Create mandatory tools – Administration/provisioning – File management – Necessary scripts for Standard • Improve existing documentation • Migrate current Maple sites – AAIT to move sites and test – AAIT to create required documentation – Site owners to test & validate 49
Tools Phase 1 • File Manager • Administration / Provisioning • Form mailer Phase 2+ • Site Builder • Templates (with DUR) • Dev-to-Prod • Point & Click provisioning • Event list • Other tools 50
More Out of Scope (Phase 2+) • Migrating Gecko to Enterprise • Create policies (in conjunction with DUR) • Applications – – – Blog Calendar Message board CMS Portal • Policy central store 51
Other related projects • Web Statistics (Governance request submitted) • Google Search (Governance request submitted) 52
Phase 1 Timeline - DRAFT Aug Sept Oct Nov Dec Finalize architecture Implement Hardware Create tools Migrate sites Test & acceptance Production ready 53
Phase 2 Schedule - DRAFT Dec Jan Feb Mar Apr Site Builder Templates Dev-to-Prod Provisioning Event List Gecko Migration 54
Outstanding issues • Finalize architecture • Determine hardware • Identify costs • Present & discuss with community • Complete & submit Level 1 CBC 55
Web Services ? Questions 56
Net. Com ? Questions 57
Скачать презентацию IT Briefing September 2006 IT Briefing Agenda
6ce4ecebd2d97b132bbb5f904811eb36.ppt