Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • No direct integration
  • Banner provides a synthesized view of data to Middleware
    • THRCSDB - person registrary info
    • SWVITSI - courses and instructors
    • SWVITRG - students and the courses they are in
  • Middleware further processes the data against the person registrary
  • Web services API is used to provision Sakai
  • Three custom java applications are used for this provisioning
    • sakai_load_users - creates the main sakai account for each user. Does not assign the user to any sites.
    • sakai_load_courses - creates all of the new course sites in Sakai. This is the process that assigns the Sakai site ID for the course.
    • sakai_load_students - adds/removes the students from each of the courses that they are assigned to

The Sakai Web Service API routines that we use are:

  • addMemberToSiteWithRole()
  • addNewRoleToAuthzGroup()
  • allowFunctionForRole()
  • checkForSite()
  • checkForUser()
  • checkForMemberInAuthzGroupWithRole()
  • removeAllRolesFromAuthzGroup()
  • removeMemberFromAuthzGroup()
  • setRoleForAuthzGroupMaintenance()
  • addNewSite()
  • addNewPageToSite()
  • addNewToolToPage()
  • addNewAuthzGroup()
  • addNewUser()

10) Did you develop the integration tool or acquired it from a third party?

...