Implementing Sun Java Enterprise System

1
Implementing Sun Java Enterprise System
2
Introductions Queen's

• 35,000 applicants
• 14,000 undergraduates
• 2,500 graduate
• 3,800 part time students
• 2,300 academic staff
• 2,400 other staff
• 17 faculties and schools
• Ranked 5th in Canada for research intensity

• ITServices (100 FTE)
• Campus Computer Sales
• Campus Telecomm and Networks
• Learning Tech/Multimedia Services
• Support Services
• Systems, Ops Network Planning
• University Information Systems
• App Dev for Admin Groups

3
Introductions Us

• Dave Hallett
• 15 years software development experience
• MBA Info Tech Mgmt
• Agile Alliance Member
• CSM
• Manager, University Information Systems

• Rich Smith
• 10 years software development experience
• Application Architect
• Project Management
• Infrastructure Services
• Senior Systems Analyst, University Information
  Systems

4
Agenda

• Why did we do this?
• Project Progress
• Implementation Details
• Success !
• Lessons Learned
• Content Management Systems
• Governance
• Collaboration
• Questions

5
Why did we want this?
6
Why?

• Two development groups in UIS
• Mainframe-based (6 people) Finance, Student
  and HR systems
• Java-based (11 people) Web application add-ons
  - Student Aid, Marks Upload, etc
• UIS needs Single Sign On and Web App Cohesion

7
Project Progress
8
Project Progress

• Winter 2004
• Interest in deploying a enterprise portal comes
  from senior management
• Look to uPortal and CAS as a solution
• Just as we starting to engage Unicon ... Campus
  EAI comes on the scene
• Spring 2005
• The case for Identity Management software becomes
  critical so combine Identity Management and
  Portal in RFP
• Send in the Vendors .... IBM, Sun and Oracle

9
Project Progress cont'd

• Summer 2005
• Decision made.
• Purchase Sun Identity Management Solution and
  Java Enterprise System.
• Complete core experiment of SSO
• Fall 2005
• Development of applications and understanding
  Portal server begins.
• Spring 2006
• Decision to implement Sun Mail (and Cal for
  Students)
• Merge Mail/Cal/Portal/SSO/IDM into a single JES
  project

10
Implementation Details
11
Key Deliverables for September

• We are application developers We don't have
  strict content!
• Let's Focus on
• Infrastructure in compliance with rest of JES
  project
• SSO opportunities for 3rd party applications
• Application integration into Portal
• Application development inside the Portal
• Set application development best practices
• If applications provide value then content
  providers will come to us.

12
Infrastructure Compliance

• JES is an integrated solution ...
• The Good
• Centralized Control of Access and Permissions
• Enhanced User Experience
• Everything is integrated
• The Bad
• Everything is integrated
• Software revisions matter of each component

13
Infrastructure Compliance

• Original September Milestone
• Portal
• Access Manager (SSO)
• Web Server (Reverse Proxy)

14
Infrastructure Compliance

• New Milestone
• Portal
• Access Manager (SSO)
• Web Server (Reverse Proxy)

• Mail
• Calendar
• IDM

15
Successes !
16
SSO Opportunities

• What do we need to SSO with?
• 3rd Party Applications
• Degree Navigator
• WebCT
• Voyager System (Library Services)
• Document Management
• Telecom Services Pinnacle
• Custom Applications
• On-line Student Registration System
• UIS Java Web Applications
• Web Servers (.htaccess)
• Others?

17
SSO - 3rd Party Applications
Reverse Proxy
Degree Navigator
QCARD
Internet
Portal
Access Manager
18
Application Integration

• Limitations?
• Screen Real Estate is Limited
• Target Content / Time Sensitive Information
• What to do?
• Take existing apps and provide task dashboards
  and provide SSO to the existing applications

19
Application Integration

• Example Library Services - Voyager
• Provide a dashboard
• SSO the Application
• Should I attempt the Sign on??

20
Application Development in Portal

• Example Course Timetable
• Web Services to Mainframe
• JSR-168 Portlet developed to render data

Mainframe
Portal Server
Oracle App Server
JSR-168 Portlet
Web Service
IMS Database
21
App Dev Best Practices

• Everything is in LDAP so how to insulate
  developers?
• Use virtual machine technology!!
• Developers get VM with RH and JES Portal/SSO/LDAP
  installed
• Gives flexibility for tear down / build up
  quickly.
• Can test application without having to be on the
  server
• CVS controlled code and server management scripts

22
Lessons Learned
23
Lessons Learned

• Understand the install prerequisites/process
• Do NOT start an uphill battle Follow
  recommendations
• Vendors will oversell
• Talk to a neutral party (non-vendor) to get the
  inside truth.
• Plan for growth
• Forget the Administration GUI

24
Content Management Systems
25
Content Management Systems

• My greatest hope is that this becomes wildly
  popular ... However, my greatest fear is that
  this becomes wildly popular -- Anonymous Coward

People like what they see and want to be 'in the
Portal' How do we get them in? We do not have a
CMS CMS that comes with Sun JES is a no-go They
don't want to write content more than once. Is it
RSS?
26
Governance
27
Governance

• A single committee
• The Student Web Directions Steering Committee
• consisting of the major stakeholders
• Office of the University Registrar, Library,
  Medicine, Advancement, Communications,
  ITServices, Student Societies,

28
Collaboration Opportunities
29
Collaboration Opportunities

• Application Development
• JSR-168 Portlets
• Problems / Solutions you have solved
• Mini-conferences
• Portlet Dev conferences?
• Sun Portal/SSO discussions of experience?

30
Questions ?
31
More Information

• Contact Us
• Rich Smith rich.smith_at_queensu.ca
• Dave Hallett dave.hallett_at_queensu.ca
• Wiki http//wiki.its.queensu.ca