1. New uPortal Contributions from the University of Wisconsin-Madison Jim Helwig University of Wisconsin-Madison Eric Dalquist Unicon, Inc. JA-SIG December 2005

2. Outline My UW-Madison Motivation Description Contributing back

3. My UW-Madison Portal Promoted as the place to go for personalized information Available to applicants, students, staff 50,000+ active accounts 1.5M logins per month Nearing end of 2 year migration from a commercial product to uPortal

4. Platform uPortal 2.5.0 Tomcat 5.0 JDK 1.4 Sun Fire v210 PubCookie Layer 4 load balancer

5. Development Strategy Maximize reuse of existing UW-Madison custom code Only limited use of available uPortal channels Implement as JSR 168 portlets Build missing APIs and services

6. Modifications, Enhancements, Add-ons Extension Libraries Portal API Abstraction Layer Common Storage

7. Modifications, Enhancements, Add-ons (cont.) Framework Extensions CONFIG Portlet Mode PREVIEW Portlet mode Extended Statistics Recorder API Abstraction Layer

8. Modifications, Enhancements, Add-ons (cont.) Personalization UI Portlets WebProxy Notepad XSL Transform Administrative Swappers

9. Extension Libraries: Portal API Abstraction Layer Database LDAP User attributes Groups Portal session Portal logger Extra information

10. Extension Libraries: Portal API Abstraction Layer Is this the Best Solution? Pros –Low implementation time –Light weight JAR Cons –Tightly coupled portlets –Classloader issues

11. Extension Libraries: Common Storage Generic attribute/object storage API Easier to use than JDBC File system like structure

12. Extension Libraries: Common Storage Backed by JDBC Does add some overhead Single point of credential configuration

13. Framework Extensions: CONFIG mode Portlet renders its own UI for publishing Useful for complex portlets (WebProxy)

14. Framework Extensions: CONFIG mode Modified CChannelManager Uses new CONFIG PortletMode Any Portlet can be used

15. Framework Extensions: CONFIG mode

16. Framework Extensions: PREVIEW mode Shows you example of fully configured portlet

17. Framework Extensions: PREVIEW mode

18. Framework Extensions: Extended statistics recorder Add portlet specific events to the stats recorder interface

19. Framework Extensions: Extended statistics recorder New stats are optional Extension to stats recorder interface Implementation is JDBC based New Events –PortletMode/WindowState change, portlet action events, channel render time, page render time,...

20. User Personalization Adds all available content to default layout UI for toggling hidden attribute

21. User Personalization Built on top of DLM Uses new preferences channel Simplifies UI customization

22. Portlets: WebProxy Works with any tag based input Manages remote session Authenticates via BASIC/NTLM/Form Based Page caching URL Re-Writing Content Clipping Proxies binary resources

23. Portlets: WebProxy

24. No well-formed XML requirement SAX filter like processing Jakarta Commons HTTP Client Flexible cache configuration

25. HTTP Client Content Filters Clipping Absolute URL ReWriting Portlet URL ReWriting Caching SAX Event Parser Web Proxy Portlet Session Management Authentication

26. Portlets: Notepad Simple note recorder

27. Portlets: XML Transform Basic XSLT transformation Can read XSL/XML from file system or URLs Configured via portlet preferences

28. Portlets: XML Transform Future Development Potential More complete XSL caching Cross-user caching

29. Portlets: Attribute Swapper UI to change user attributes dynamically Look up other users to copy attributes from

30. Portlets: Attribute Swapper

31. Portlets: ID Swapper Assume identity of any portal user Configure which attributes are used for look up

32. Portlets: ID Swapper

33. Contributing Back Bug fixes in Work on incorporating non- obtrusive framework modifications Add others to JA-SIG CVS When?

34. Thank You, JA-SIG!

35. Questions? Jim Helwig jim.helwig@doit.wisc.edu University of Wisconsin-Madison Eric Dalquist edalquist@unicon.net Unicon, Inc.