6:
Re: Advice on how to communicate with an external tool
By: Marcin Cieslak
|
In response to 1 | 11/03/08 07:27 PM | ||
Hi Daniel,
you don't need a direct DB access to get user list from a tool. If you want a list of learners and teachers that will participate in a lesson, you'll need the LessonService. Most of the tools didn't need access to its functionality, but if you take a look at SubmitFiles tool from HEAD, you'll see that LessonService was injected into tool's service in order to get a list of monitoring teachers. I guess there is no method that allows you to get a list of learners, but if it's really needed, we can implement it and add it to the service. A tool itself knows only about the learners that actually reached it. The moment a lesson is started, a new instance of tool content is created. If there is no grouping, a tool session that will hold the whole class is created. But if there is grouping like Choose in Monitor, learners will be divided into several sessions. There is no way to learn to what session a learner will be assigned to before he/she will reach the tool. In fact, sometimes sessions are created the moment a learner reaches the tool. In order to get user info from a tool service, usually there are methods like (based on SubmitFiles tool service): Parameters are provided by the progress engine, so just check the code for examples how to use those methods. Then you can add your own method that will create a XML file that can be read by your external application. So, when you write: "when the teacher starts a lesson the server writes a file with the info on what the users and groups" - when a lesson is started, you can get a list of learners that MIGHT (but might not, if there is branching) get to your tool. There is no way you can tell what groups they will be in at this moment. If you have any questions, just let us know. Posted by Marcin Cieslak |
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
Reply to first post on this page
Back to LAMS for Tech-Heads - General Forum