The rSmart Group JA-SIG 2007 All Materials © 2007 The rSmart Group Sakai - SIS Integration Using Data Extracts John Bush The rSmart Group JA-SIG June 2007

The rSmart Group JA-SIG 2007 All Materials © 2007 The rSmart Group Typical Sakai Integrations User Provider Group Provider Course Provider

The rSmart Group JA-SIG 2007 All Materials © 2007 The rSmart Group Using Providers Find and modify or create an implementation Figure out how to “talk” - directly access external db, staging tables, web services, messaging (ESB), etc Deploy into Sakai’s component tree

The rSmart Group JA-SIG 2007 All Materials © 2007 The rSmart Group Using Data Extracts Dump SIS data into files Make extracts available to the Sakai system (file share, scp, ftp, etc) Create a Job to process the extracts

The rSmart Group JA-SIG 2007 All Materials © 2007 The rSmart Group rSmart CLE csv files representing user, site, and membership data Quartz job sync’s the data

The rSmart Group JA-SIG 2007 All Materials © 2007 The rSmart Group Job Scheduler in Sakai Built on quartz –Create a Job –Deploy via Sakai’s component manager Scheduler tool provides UI –Cron like scheduling –Pick job and set a trigger SAK-6968

The rSmart Group JA-SIG 2007 All Materials © 2007 The rSmart Group Creating a Job public interface Job { void execute(JobExecutionContext jobExecutionContext) throws JobExecutionException; }

The rSmart Group JA-SIG 2007 All Materials © 2007 The rSmart Group abstract public class AbstractAdminJob implements Job { /** * Child classes should implement their work in this guy. jobExecutionContext JobExecutionException */ protected abstract void executeInternal(JobExecutionContext jobExecutionContext) throws JobExecutionException; /** * Switchs the current user to the adminUser and pushes a SecurityAdvisor onto the security stack to avoid authz issues. * Then we invoke executeInternal, and switch the current user back. jobExecutionContext JobExecutionException */ public void execute(JobExecutionContext jobExecutionContext) throws JobExecutionException { logger.info(this.getClass().getName() + " starting..."); Session sakaiSession = sessionManager.getCurrentSession(); String currentUserId = sakaiSession.getUserId(); sakaiSession.setUserId(adminUser); sakaiSession.setUserEid(adminUser); SuperUserSecurityAdvisor securityAdvisor = new SuperUserSecurityAdvisor(); securityAdvisor.setSuperUser(adminUser); securityService.pushAdvisor(securityAdvisor); Date now = new Date(); executeInternal(jobExecutionContext); Date later = new Date(); sakaiSession.setUserId(currentUserId); sakaiSession.setUserEid(currentUserId); logger.info(this.getClass().getName() + " finished in " + (later.getTime() - now.getTime()) + " millis"); }

The rSmart Group JA-SIG 2007 All Materials © 2007 The rSmart Group Wiring up your job in Sakai <bean id="com.rsmart.sis.scheduler.job.CustomerIntegration" class="org.sakaiproject.component.app.scheduler.jobs.SpringJobBeanWrapper" singleton="true" init-method="init"> customerIntegrationJob rSmart Customer Integration Job -->

The rSmart Group JA-SIG 2007 All Materials © 2007 The rSmart Group User Data EID - Enterprise ID Last Name First Name Password User Type User ID

The rSmart Group JA-SIG 2007 All Materials © 2007 The rSmart Group Site Data Semester - stored as site property Site ID Start Date - stored as site property Name or Title Description - shows in site list Long Description - shows on home page Published End Date - stored as site property Site Master

The rSmart Group JA-SIG 2007 All Materials © 2007 The rSmart Group Membership Data EID -Enterprise ID Site ID Role

The rSmart Group JA-SIG 2007 All Materials © 2007 The rSmart Group Demo

The rSmart Group JA-SIG 2007 All Materials © 2007 The rSmart Group Disadvantages of this approach Large datasets can be slow Doesn’t support a rich model Need to deploy some code in Sakai Not realtime