IT Briefing

September 2006

2

IT Briefing Agenda 9/21/06

• SWE Updates

• Manage IT Upgrade

• Blackboard Overview

• Web Approach

• NetCom Q&A

• Karen Jenkins

• Karen Jenkins

• Sandra Butler

• Karen Jenkins

• 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

3

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?

Manage IT

Karen JenkinsAndrew KincaidAl Shelton

5

Remedy Modules

ActionRequestSystem

ChangeManagement

Service Desk

ServiceLevel

Management

AssetManagement

6

Architecture

Web/Mid-Tier Server

Application ServerDataBase

Server

eGenera2 x Intel Xeon P4 3 GHz6 GB RAM

eGenera4 x Intel Xeon P4 3 GHz12 GB RAM

Sun 4804 x 900 MHz

16 GB RAM

`

Windows client

access

Web access

7

Remedy Upgrade – Heads up!

• Major new release v7.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

8

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

9

10

11

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 auto-

approve – so process is not bogged down

• Save high risk changes for CAB

12

13

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

14

Input & Schedule

• First TechTalk tomorrow 2:00-3:30 NDB 225 Kennesaw– 10/13, 11/3, 11/24

• Will also updates at IT Briefing

• Target installation => October• Go-live => TBD• Initial scope = migrate current

functionality & data

15

?Questions

Manage IT

Blackboard @Emory

Sandra ButlerManager, Interactive Technologies Team

IT Briefing 09/21/06

17

Interactive Technologies Team

• Adam Lipkin• Marcy Alexander• Tricia Goddard• Kathy Hayes

• David Lower• Julia Leon• Marianne Schneider• Open Slot

18

Interactive Technologies

• LearnLink• Blackboard

– classes.emory.edu

– classes@emory.edu

• Insight• Wimba

19

What is Blackboard (Bb)?

• Academic Suite– Learning

System– Community

System– Content System

• Building Blocks– Add-ins that

extend capability and functionality

20

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

21

History: Bb at Emory

1999: review Bb CourseInfo versus WebCTteaching & learning at anytime from anywhere

2000: University adopts Bb 5; upgrade to Course & Portal Managerdepts, orgs, and clubs; customizable buttons; building blocks announcement (Bb Inc.)

2002: upgrade to Bb 5.5 EnterpriseBb app server & Oracle db server; move to 24/7 data center; custom script for enrollment; Emory’s GenLib 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

22

2005: license Content System; SSL & load balanced; upgrade to Bb 6.2file mgmt; content sharing; ePortfolios; passes to entire community and guests; Wimba Building Block trial

2006: Reorganize / AAIT / ATS / Interactive Technologiesapp 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 resourcesreview overall structure: enhance processes; improve infrastructure

History: Bb at Emory

23

Bb at Emory Stats 09/18/06 2:00pm

• 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

24

0 1000 2000 3000 4000

Aug-02

Aug-03

Aug-04

Aug-05

Dec-05

Current

Courses Orgs

Bb at Emory Stats 09/18/06 2:00pm

25

Bb Course Site

26

Building Block: Wimba Voice Tools

27

28

Bb & Insightintegration made easy

29

https://classes.emory.edu

Proposed Web Approach

September 2006

31

Agenda

• Current environment• Initial plan• Revised plan• Architecture goals• Draft architecture• Estimated timeline• Outstanding issues

32

Gecko & Maple

• Focused on the needs of the hard core developer community

• Maple Issues:– Difficult to support & maintain due to

multiple customizations (Apache, “ITD WebDrive”)

– Security issues– Old hardware

33

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

34

Stabilize

• Split SiteMinder / non-SiteMinder 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

35

Community Requirements

• Developers only need a couple of additional features:– MySQL, 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 …

36

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

37

Web Approach

• 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

Tiered service offerings dependant upon user needs

FUTURE STATE

39

Hosting Options

Service & Support

Standard

Advanced

Enterprise

Backup/Restore

Server maint.

Proactive Monitoring

System admin.

High avail.

Web Workshops

Assigned POC

40

Hosting Options (cont.)

Features & Tools

Standard

Advanced Enterprise

Templates

Site builder

Script library

Site statistics

Google search

Error/log files

Virtual servers

41

Hosting Options (cont.)

Features & Tools (continued)

Standard

Advanced Enterprise

sFTP

File Manager

SSH (dev)

Cronjobs

Dev/QA Env.

Dev-to-prod

Disk space 500 MB 1 GB 2 GB

42

Hosting Options (cont.)

Site & Application Development

Standard

Advanced Enterprise

HTML

PHP 4.3.2

Cold Fusion 7.1

Perl 5.8

Python 2.3

J2EE

SiteMinder

43

Hosting Options (cont.)

Database Development

Standard

Advanced Enterprise

Oracle

MySQL

Cold Fusion Connectors

Oracle

MySQL

Microsoft SQL

RAC JDBC

44

Hosting Options (cont.)

Applications

Standard

Advanced Enterprise

Blog

Calendar

Message Board

CMS

Portal

Architecture--DRAFT--

46

Architecture Goals

• Low entry-barrier• Consolidate where possible• Improved isolation / management• Seamless scalability• Highly secure• High stability, availability, and

performance

47

9/20/2006Version 1.0 AAIT

DRAFT - Web Architecture

Web access Academic Network

DMZ Network

Admin Core Network

Enterprise Web ServersLDAP Proxy

OracleDatabaseServersWeb

Application Servers

Load Balancers w/ HTTP proxy

Network Attached Storage

Standard & Advanced Web Servers

SSL Termination

Reverse Proxy

MySQLDatabaseServers

48

9/20/2006Version 1.3 AAIT

DRAFT - Software Configurations

Apache 2.0JRun 4.0CF 7.1Perl 5.8PHP 4.3Oracle 10.2MySQL 4.0

Advanced Hosting

Apache 2.0HTML 4.0

Standard Hosting

Apache 2.0WebSphere 5.0CF 7.1Perl 5.8PHP 4.3Oracle 10.2

Enterprise Hosting

Apache 2.0Jboss J2EE 1.4Oracle 10.2MySQL 4.0

One shared instance

Multiple dedicated containers

Apache 2.0JRun 4.0CF 7.1Perl 5.8PHP 4.3Oracle 10.2MySQL 4.0

Apache 2.0WebSphere 5.0J2EE 1.4Oracle 10.2MySQL 4.0

Apache 2.0WebSphere 5.0CF 7.1Perl 5.8PHP 4.3Oracle 10.2

Multiple dedicated containers

Utilize Resource Management to allocate resources (CPU, memory, processes, etc.) to each instance

Project Scope

Phase 1 and beyond

50

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

51

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

52

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

53

Other related projects

• Web Statistics (Governance request submitted)

• Google Search (Governance request submitted)

54

Phase 1 Timeline - DRAFT

Finalize architecture

Implement Hardware

Create tools

Migrate sites

Test & acceptance

Production ready

Sept Oct Nov DecAug

55

Phase 2 Schedule - DRAFT

Site Builder

Templates

Dev-to-Prod

Provisioning

Event List

Gecko Migration

Jan Feb Mar AprDec

56

Outstanding issues

• Finalize architecture• Determine hardware• Identify costs• Present & discuss with community• Complete & submit Level 1 CBC

57

?Questions

Web Services

58

?Questions

NetCom