1. uPortal.Cornell Using uPortal to integrate disparate campus systems Jon Atherton, Cornell Information Technologies jca8@cornell.edu

2. Outline Infrastructure Where we started The Vision Implementation goals A New Face Where we are heading

3. The Infrastructure Authentication (Kerberos) Kclient SideCar CUWebAuth Authorization (Permit server) Software Distribution (Project Salsa) Directory (LDAP)

4. Where we started Bear Access CUinfo Dozens of web sites Legacy applications Single Sign-on in place PeopleSoft 8 Blackboard

5. Roles Maintain Framework (CIT) Bear Access uPortal Content Publisher (CIT) Packaging & Delivery group Content/Service Providers (Campus wide) Library- Campus Store Registrar- CIT

6. The Vision Improve access to current & relevant information Create the next generation enterprise point of entry Bear Access CUinfo Maintain current roles

7. Implementation goals Leverage existing infrastructure Authentication (Kerberos single sign on) Authorization (permit service) Software distribution (Project Salsa) Directory (LDAP) Deliver Existing Services Minimal modifications to uPortal source

8. uPortal.Cornell Single Enterprise point of entry Integrate existing services Window into larger applications Aggregate resources Pull in external resources Personalized & Customizable

9. Putting on a new face

10. Bear Access First released in 1992 Deployed to all staff, students & faculty Provides software distribution Access to licensed software Limited customizability

11. Bear Access channel Jsp based CWebProxy channel Can display content based on group (permit) membership Provides software distribution capability User customizable

12. CUinfo Originally a terminal based mainframe app Then became a gopher site Currently is an Index to web sites Also contains Web apps

13. CUinfo Browser channel CWebProxy channel Hierarchical menu of CUinfo content

14. Student Jobs Web application written in REXX accessing mainframe content using proprietary protocol

15. Student job listings channel Jsp based CWebProxy channel New interface to existing back-end application

16. Permit maintenance page Web pages used to maintain permit groups Difficult to use

17. Group maintenance channel New interface, allowed non-techies to maintain permit groups Contains most of the functionality of web pages

18. Administrative Services channel Provides access to PeopleSoft 8 Based on LaunchPad channel

19. Library Gateway channel Hosted by Library Provides same access as “Library Gateway” web site.

20. CERT Advisories channel.rss channel provided by CERT

21. Employee Essentials Currently exists as a web app Reads from database Updates to Peoplesoft via WebMethods and PS8 component interface

22. More about … Employee Essentials Collaborative effort between CIT and HR CIT built data access components as jsp’s HR built web app using jsp’s Components have been reused in other apps webMethods Integration broker Enables disparate systems to share information in a common manner Central control and storage point that mediates events to and from applications

23. New EE channel See demo Currently prototyping Will be joint effort again This time CIT will write Web Services (SOAP) to access appropriate data HR is developing using Cold Fusion

24. Where we are going

25. Roles Maintain Framework (CIT) Bear Access uPortal Content Publisher (CIT) Packaging & Delivery group Content/Service Providers (Campus wide) Library- Campus Store Registrar- CIT

26. Evolving Roles Maintain Framework (CIT/Infrastructure) uPortal upgrades Develop new infrastructure channels Content Publisher (CIT/Packaging & Delivery) Coordinate between content/service providers and infrastructure group Content/Service Providers (Campus wide) Content Working Group

27. Demo Bear Access uPortal.Cornell Bear Access CUinfo Browser Student Jobs Group Maintenance Library Gateway CERT Advisories Administrative Services

28. http://guest.uportal.cornell.ed u