...
- The Collaborations tab has a single portlet on it.
- The worksite tabs are generated by the portlet.
- The rest of the Sakai layout sits in an iframe generated by the portlet.
- This models the use of iframes in Charon, the Sakai portal.
- Authentication into Sakai is transparent to the user.
- Load balancing complicates shared authentication.
- Because our Sakai is in pilot (and our portal is not) only pilot users see the "Collaborations" tab.
- This is accomplished via the uPortal Groups infrastructure (GAPS), a custom PersonAttributesDAO, Sakai webservices and DLM.
- We are using DLM as a layout manager, but this should work with ALM too.
- Sakai is running as a portlet inside uPortal, but there is no portlet "decoration" around it.
- This required a trick using a portlet/channel parameter and a modified theme stylesheet
- The javascript in Sakai puts some constraints on how the iframe integration is implemented
...
There is a hardware loadbalancer (Cisco LocalDirector) in front of the Apache servers.
See Appendix: uPortal Configuration Details
Sakai Server Configuration
...