Notes on integration between SUM component and Switched On Sponsorship system

[Richard Newbould]

This email summarises the above discussion between:

Pete Smit

Farayi

Richard

 

SUM = Switched On User Management -> for managing user accounts in the training centres. e.g. for login, access to Moodle courses

Sponsorship system is for passing messages back and forth between students and sponsors

 

There is overlap between these. Thoughts on how to integrate:

• Must be non-realtime sync because cannot rely on network to training centres => use a messaging protocol such as JMS (Jave Messaging Service)
• Allow the systems to be developed somewhat independently => don't integrate at the database level.  Scripts at adaptors/business logic level must handle translation/changes to structure of data.
• Non-the-less simplify integration by using same user IDs 
• Use SUM as master for student data in longer term so not need bi-directional updates/sync issues

Practical way forwards - Richard implement Sponsorship system prototype and then share with Pete & Farayi for discussion on how align the two.

 

 

Cheers,

 

Richard