Luminis Technical Planning Workshop – Day 1 – Notes

Some notes from the Luminis meeting…

Overview

It’s a Portal! Personalized content for end users. Role based content for channels. Roles can be specified from Banner.

Luminis uses uPortal for front end. Web management CMS is driven by Documentum.

Built in portal features / channels

• E-mail
• Calendar – JES calendar system.
• Targeted announcements for roles / user groups via channels. Personal announcements for individuals based on some targeted factor. Campus announcements for all Luminis users.
• Course studio – SIS / not replacement for Blackboard. Probably useful as single sign on for Blackboard.
• Group Studio – Ad hoc groups. Clubs, committees… messaging for group or club collaboration. Can be flexible for student organizations. Users must be authenticated for Luminis to access Groups, so no public Internet groups, or public access to group content. File sharing, content management, chat, e-mail distribution, targeted announcemments.

Luminis features

• Password recovery – Question and answer system followed by request to change password on screen. User or system defined questions and answers.

Project Timeline

Luminis:

• Assess
• Plan – We are currently here.
• Implement
• Re-assess

Nicholls:

• Prospective Students – September 2008
• Finance – July 1, 2009

Sungard Higher Education Support: https://connect.sungardhe.com/

Single Sign On

• Web
• Internet Banner
• Blackboard
• Groupwise
  Display short list of new messages. Allow click to sign on to groupwise from Luminis Portal. Chris Usey already has used IMAP component in Luminis to display new messages in portal.  Chris currently has click then authenticate to Groupwise Web.
  • Student e-mai, Web access, Home Dir.
  • Staff
• E-Print
• AdvisorTrac
• TutorTrac
• Colonel Card – Blackboard One Card

Best Practice: Use of external directory service for Luminis authentication.

Best Practices

• Username and e-mail formats
  • Student tree
  • Staff tree

Development

Five SDK Development Kits. Lumdev – development community for Luminis.

• CDK  – Channel Development Kit – User Interface – Java – XML based.
• Communication – targeted announcement etc.
• Security – authentication against other systems and build your own.
• Data Access – Set and Access data from luminis.
• Data Integration – to pre-populate other systems.
  Nicholls: has Blackboard Integration.

Single Sign On – SSO

GCF vs. CPIP - Generic Connector Format (GCF) – XML based. Built by researching the connection / authenticaiton / session between servers. CPIP – more intensive java based connector – you should have source to really understand sessions, authentication, timeouts, etc.

LDIS - Communication with other systems via Luminis Message Broker.

“Secret Store” – stores and manages credentials for external systems.

Luminis Usename + Luminis Password > MD5 > RSA key > encrypt. Secret Store recovery can be managed by agents to allow or deny Secret Store reset. Most systems allow automatic recovery.

Integration

Builtin integration for channels and applications for Sungard; Banner, Student / Staff Self Serve, etc. Some supported integration channels for 3rd party such as Groupwise and Blackboard.