Sakai/OSP Portfolio UvA Bas Toeter Universiteit van Amsterdam

Agenda Infrastructural Architecture –File storage, Database, –LDAP, , sizing. Customization –Sites, Roles, –Realms, Permissions. Software Development Aspects –Development, deployment.

Amsterdam Piloted with OSP 2.0 in 2005 / 2006 –Worked on internationalization and testing –Set up a QA server with automated testing –Documented a couple of tools Sakai 2-2-x production since January 07 –Worked on OSP bug fixing and testing –Set up a QA server Sakai 2-4 –Worked on OSP requirements –Some testing We have a Portfolio only implementation

Infrastructural Architecture Sizing –How may users do what at the same time? –cpu, memory, storage, database, bandwidth –Load balancing Enterprise Integration –File Storage –Mail –Database –User management / Authentication

Sizing Guestimates: Current numbers –637 users –62 MB database –449 MB uploaded files Dual 3.4Ghz CPU 4GB memory Redundant storage YearProgramsUsersConcurrentFile storageDB storage GB1440 MB GB3780 MB TB8250 MB

Load balanced infrastructure

Two Cisco content switches –(Which are a pain to configure) –Running in failover mode Sessions are sticky –Users need to keep going to the same instance No true clustering, just load balancing Offloading SSL

sakai.properties # identify your application server with a short name, un… # choose a server id even if you are running a single a… serverId=bomans # the URL to the server, including transport, DNS name,… serverUrl= # force all URLs out of Sakai back to Sakai to be secure… # Otherwise, the URLs will reflect the attributes of the… force.url.secure=443 # For OSP, only set auto.ddl = true on one cluster server auto.ddl = true | false

File Storage Files stored on Storage Area Network –Network Storage mounted on a fileserver –Using NFS between members and fileserver –Reduced storage overhead through many ‘small’ (~800GB) volumes (lowers cluster size)

sakai.properties # root of archive file system area - used to write… # when clustering app servers, this should be a sh… # = /home/portfolio-files/sakai/archive # when storing content hosting's body bits in file… # to act as volumes to distribute the files among … # see the readme file (2.2.7 File Based Content Ho… = volume1 # Site quota setting (KB) =

Mail Integration Outgoing mail –Goes out through a local sendmail –‘Smarthost’ configuration Portfolio server Local sendmail process Corporate SMTP servers

Mail Integration Incoming mail –Not doing this …. yet –May do something like this: Portfolio server Local sendmail process Corporate SMTP James

Mail Integration Incoming mail –Or simpler: Portfolio server Local sendmail process Corporate SMTP James

sakai.properties # smtp server for outgoing s # address to send errors caught by the portal… #setup request; from address for s to users about… # flag to enable or disable James for incoming … smtp.enabled = false

Database Size (oversized multipurpose db) –SUN V GB physical - 4 dual core UltraSparc 1200 MHz running Solaris 8 2/04 s28s_hw4wos_05a SPARC. –Oracle JDBC Driver –ojdbc14.jar v ( bytes) AL32UTF8 Character set

User Management User creation via a tool –Controlled rollout LDAP authentication –Implemented a UserDirectoryProvider –Supports fallback and multiple domains –Does not create accounts

The big picture..

Customization –Gateway site –Different My workspace’s –Managing site types –Delegated site creation –Realms, Roles, Permissions

Customize your Gateway Gateway is a site defined in !gateway Use the Sites tool to modify

Diversifying the My Workspace Different users have different needs and get different tools…..defined in ‘site template’

The effect of Type on My Workspace

Sites Choices in setting up portfolio sites –Portfolio in My Workspace ? –One Portfolio site per student ? –A site per study program? –Site per study program per year? Presentation and Matrix tools in different sites? Leave it up to faculty !

Portfolio sites Defined as a category in toolOrder.xml

Allowing local admins to create Portfolio sites (only) Use Sites tool to open local_admins my workspace template

Allowing local admins to create Portfolio sites (only) Scroll down and open ‘Pages’ section

Allowing local admins to create Portfolio sites (only) Open the ‘Worksite Setup’ page Click on the tool id of the sakai.setup tool Scroll down to ‘Configuration’

Allowing local admins to create Portfolio sites (only) Remove siteTypes ‘project’ and ‘course’

Realms define Roles… Define roles in site template realms OOTB: !site.template.portfolio Reuse or modify

…and Permissions For Sakai tools not (yet) for OSP tools

OSP Tool Permissions Can be defined in sakai.properties # Glossary tool permissions glossary.permissions.override=false glossary.permissions.map.count=1 glossary.permissions.map.1=Coordinator glossary.permissions.map.1.siteTypes=portfolio glossary.permissions.map.1.value.count=4 glossary.permissions.map.1.value.1=osp.help.glossary.delete glossary.permissions.map.1.value.2=osp.help.glossary.add glossary.permissions.map.1.value.3=osp.help.glossary.edit glossary.permissions.map.1.value.4=osp.help.glossary.export

Software Development Aspects Basic idea –Being able to test, and accept before moving into production –Script as much as possible –Create a simple deployment process

Develop, Test, Accept, Run!

Script as much as possible DEVPRDACC

Simple Deployment Process /etc/sakai/sakai.properties /etc/sakai/toolorder.properties /usr/local/tomcat1/ sakai.properties toolorder.properties tomcat1/ portfolio_prd-r _16.34.tar.gz Deployment file contains Tomcat and Config files

Todo.. Upgrade to Sakai 2.4 Move to virtualized hardware Externalize authentication Connect to IDMS and CAS

Questions..?