1. From Your Course Syllabus to Earthquake Engineering: Collaboration using the CHEF Framework Charles Severance University of Michigan

2. Outline Collaborative Activities at UM CHEF Technology CHEF Features CHEF Status The Sakai Project Sakai Technologies Sakai Timeline

3. Collaboration @ UM 19981991 - 19971999200020012002200320042005 SPARC Science of Collaboratories Sakai Worktools (Notes Based)WTNG Coursetools (Notes Based) CTNGCHEF 1CHEF 2 NMI Grid Portal NEESGrid

4. SPARC 2/2001 600 users 800 data sources

5. CourseTools Over 42,000 users at the end of 2003

6. WorkTools Over 9000 users (2000 active) at the end of 2003

7. Digital libraries & documents groups-to- information groups-to- facilities people-to-people Communication, Collaboration Services Distributed, media-rich information technology Remote instruments http://www.scienceofcollaboratories.org/ Science of Collaboratories NSF Funded ITR

8. CHEF 1.0 Fall 2001: CHEF Development begins –Generalized extensible framework for building collaboratories –“Best-of” CourseTools, SPARC, WorkTools Integrate across current UM projects and adopt relevant standards Funded internally at UM as replacement for CourseTools All JAVA - Open Source –Jakarta Jetspeed Portal –Jakarta Tomcat Servlet Container –Jakarta Turbine Service Container Build community of developers through workshops and outreach

9. CHEF Technology Provide a mechanism for software development which will allow organizations to share and re-use each other’s work Utilize existing technologies wherever possible and add value rather than invent all new Enable code reuse across multiple organizations Lead to portal technology - Jetspeed

10. Not “just” a portal Portals are a framework to deploy tools (aka rectangles) and focus on how the user wants to arrange their own “rectangles” While CHEF technically is a portal, the goal is for the tools to work together closely and seem to really be parts of a larger “tool” CHEF has a lot of features, (services, presence, notification, etc..) which bridge the gap between portal and application framework

11. CHEF General Tools –Announcements –Chat –Threaded Discussion –Calendar –Schedule –E-Mail Archive –Resources (including WebDav) –Web-Frame –Worksite Setup –Profile –Notifications / Subscriptions –Public View –Anonymous Comment

12. CHEF - More tools Course Management –Assignments –Drop Box Worktools –Data Viewers (Live/Stored) –Telepresense –Video as Data –Electronic Notebook Grid Technologies –Grid sign on using myproxy –Grid computational portal –GridFTP –..Many more

13. CHEF Implementation Architecture - More Detail Tomcat Servlet Container Jetspeed Portal Turbine Framework Tool Turbine Service Velocity CSS Turbine Service Turbine Service Servlet In addition to Jetspeed, CHEF operates within a Servlet container called Jakarta Tomcat. Whereas portlets operate in one “recatangle” which is a subset of the screen, Servlets control the entire HTTP response or even talk non-HTTP protocols.

14. Example Architecture - Resources Tomcat Servlet Container Jetspeed Portal Turbine Resource Tool Security Service Velocity CSS Content Service User Dir. Service Access Servlet src/java/org/chefproject/actions/ResourceAction.java src/vm/chef_resources_show.vm (plus 10 more) src/java/org/chefproject/service/component/BaseContentService.java src/java/org/chefproject/service/component/BaseUserDirectoryService.java src/java/org/chefproject/service/component/ChefSecurity.java src/java/org/chefproject/servlet/ChefdavServlet.java src/java/org/chefproject/servlet/AccessServlet.java HTTP Webdav Servlet WEBDAV

15. Services Long-term lifecycle One instance (Singleton) –Must be aware that multiple users can use service –Can use memory resident information (often used for cache) Contains as much of the implementation as possible Pluggable implementations –Memory version –XML implementation –Web services implementation –Database implementation

16. Service Implementations Tool Service API Clustered Service Implementation Portal Engine Web Svcs Service Implementation Database Service Implementation The API is an Interface – There can be any number of different service implementations which implement the Interface. At run-time Turbine reads a configuration file and associates the appropriate service implementation with each API and provides lifecycle services to the service. Turbine Service Broker chef.properties

17. Tools Grid Service API CHEF Grid Service Component UserDirectory CHEF UserDirectory Service Component Grid UserDirectory Provider Service UserDirectory Provider Existing CHEFNew Code Existing GRID IU Portlets LDAP GridFTP Proxy Jetspeed User IU Code Jetspeed Login COGs MyProxy Tomcat / Apache Adding Grid Infrastructure to CHEF

18. CHEF Applications CourseTools Next Generation WorkTools Next Generation NEESGrid NSF National Middleware Grid Portal

19. CourseTools Next Generation Over 5000 users at the end of 2003 http://coursetools.ummu.umich.edu/

20. Worktools Next Generation New WorkTools Sites being created in WTNG as of 12/2003 Run on the same servers as CTNG.

21. NEESGrid - The Equipment Network for Earthquake Engineering Simulation NSF Funded. NCSA, ANL, USC/ISI, UM, USC, Berkeley, MSU

22. CHEF-Based NEESGrid Software

23. NMI / OGCE www.ogce.org NSF National Middleware Iniative Indiana, UTexas, ANL, UM, NCSA

24. CHEF Status CHEF is stable and released –CHEF 1.2 from www.chefproject.org –Workshops twice per year –Technical support mailing list –Collaborative site chefproject.org/chef/ Other derived variants of CHEF –NMI 1.0 Beta from www.ogce.org –NEESGrid 2.1 from www.neesgrid.org

25. What is Next: SAKAI U Michigan, Indiana U, MIT, Stanford, uPortal –All have built portals / course management systems –JSR-168 portlet standard requires us all to re-tool and look at new approach to portals Course Management System Standards –Open Knowledge Iniative (OKI) needed full implementation –IMS standard such as Question and Testing Interoperability (QTI) Why not coordinate this work, do the work once, and share each others solutions? Integrate across projects at multiple institutions and adopt relevant standards Collaboration at the next frontier - implementation Tool Portability Profile (TPP) –Truly portable tools and services –Tools built at different places look and feel the same and share data and services –This is difficult - Interoperbility is harder than portability Mellon Foundation funding

26. Open/Open Licensing “..all work products under the scope of the Sakai initiative for which a member is counting matching contribution and any Mellon Sakai funding” will be open source software and documentation licensed for both education and commercial use without licensing fees.

27. Jan 04 July 04May 05 Michigan CHEF Framework CourseTools WorkTools Indiana Navigo Assessment Eden Workflow Oncourse MIT Stellar Stanford CourseWork Assessment OKI OSIDs uPortal SAKAI 1.0 Release Tool Portability Profile Framework Services-based Portal Refined OSIDs & implementations SAKAI Tools Complete CMS Assessment SAKAI 2.0 Release Tool Portability Profile Framework Services-based Portal SAKAI Tools Complete CMS Assessment Workflow Research Tools Authoring Tools Primary SAKAI Activity Architecting for JSR-168 Portlets, Refactoring “best of” features for tools Conforming tools to Tool Portability Profile Primary SAKAI Activity Refining SAKAI Framework, Tuning and conforming additional tools Intensive community building/training Activity: Ongoing implementation work at local institution… Dec 05 Activity: Maintenance & Transition from a project to a community SAKAI Overview

28. Portability Profile (as of today) Tools –JSF GUI Layer –JSR 168 Portlet –JSR Servlet Standard Services –Level 1-3 Inversion of Control –Avalon, Turbine, OKI, Spring, Pico J2EE / EJB / JBoss - Enterprise Services –Stateless Session –Entity beans for clustering and scaling This is in progress - so it may change

29. Sakai Architecture Portal Technology uPortal 3.0 Portal Configuration Implementations Channels, Teamlets JSR-168 Portlets CHEF Services JSR-168 Technology OKI Services Legacy Sakai Teamlet Other Services Sakai GUI Portable code Sakai Service Layer Sakai GUI Layer Mega-portable code

30. Sakai Timeline Dec 15 SAKAI 1.0 Whitepaper Pre-alpha release of SAKAI’d CHEF Architect Discussions: getting it right across schools Oct ‘03Oct ‘04Jan ‘04Apr ‘04July ‘04 Architecture and Tool Development Tool Development July 1 SAKAI 1.0 available for testing by production facilities Feb 15 SAKAI 0.5 available for tool development July 1 Final tool delivery to participating schools Feb 1 Deliver full spec to programmers Feb 15 Developers’ Workshop: Coding SAKAI 1.0 using SAKAI 0.05 Nov 15 Requirements, Functional Design, UI, Full Spec Aug 1 Tools running in SAKAI 1.0 pilot/production environment at participating schools

31. Summary