Note that neither Docent nor TotalLMS have this functionality built in, so the question would be to see if it could be added in some way.
Since Docent doesn't really have a concept of 'logging out' at all (at least as an accessible option in the user interface), you'd have to make some assumptions as to that defines a 'logged in user' as a function of the data that is available, namely the data available in the DESession table. Now, according to the Docent documentation, dead sessions are supposed to be cleared from this table, but there sure seem to be plenty of dead sessions in mine.
For TotalLMS, since it uses ASP, we can get some information from the server operating system. I haven't figured out how to determine who they are yet, but you can get a count of the number of sessions the system thinks are currently active by monitoring the "Sessions Current" counter of the "Active Server Pages" object using Performance Monitor. You can set up a performance log for this to see how the number of active sessions changes over time.
Ok, here's an example of SQL code that is needed to generate the list of logged in users. Note that the time period used to eliminate 'stale' users is adjustable based on whatever assumptions you'd like to make. If a user uses the 'logout' function in the LMS, the LMS session goes away immediately, but if they merely kill their browser or shut down without logging out, they will appear to still be logged in, apparently indefinitely. Anyway, here's the SQL:
SELECT *
FROM TBL_User
WHERE (LoggedIn = 1) AND (LastLoginDate > DATEADD([day], - 1, GETDATE()))
This assumes anyone who logged in more than a day ago is 'stale' rather than a current user. Now of course, getting this into the system in some way you can execute it is the trick to solve. If the necessary columns are exposed to ReportManager, that may be an option. I haven't played with ReportManager enough to know that.
Ok, I was able to get this basic data using ReportManager. I had to add a datasource for the production database (as looking in the replicated data would be fairly meaningless), and that worked for getting at the appropriate table. Filtering out based on the value of LoggedIn was easy, though I haven't figured out how to set up the filter for 'stale' data.
Hi Reading the above comments, does 7.X still use the same behaviour as Docent in terms of keeping sessions active after someonehas closed their IE window?
Yes, I have tested this with 7.2, the TotalLMS system doesn't notice when the user leaves 'ungracefully' --- closed browser, dropped network connection and so forth. The logged in status seems to persist in the database indefinitely.
Now, IIS/ASP seems to be able to track this somewhat better, using the performance monitor will show that the ASP session is dropped when the browser window closes. I haven't checked to see what happens or how long it takes/if IIS/ASP will time those out at some point, but I'd imagine it would.
--
Joe Kyle
--jjkd--
See active (logged in) users
Note that neither Docent nor TotalLMS have this functionality built in, so the question would be to see if it could be added in some way.
Since Docent doesn't really have a concept of 'logging out' at all (at least as an accessible option in the user interface), you'd have to make some assumptions as to that defines a 'logged in user' as a function of the data that is available, namely the data available in the DESession table. Now, according to the Docent documentation, dead sessions are supposed to be cleared from this table, but there sure seem to be plenty of dead sessions in mine.
For TotalLMS, since it uses ASP, we can get some information from the server operating system. I haven't figured out how to determine who they are yet, but you can get a count of the number of sessions the system thinks are currently active by monitoring the "Sessions Current" counter of the "Active Server Pages" object using Performance Monitor. You can set up a performance log for this to see how the number of active sessions changes over time.
--
Joe Kyle
--jjkd--
See active (logged in) users
Ok, here's an example of SQL code that is needed to generate the list of logged in users. Note that the time period used to eliminate 'stale' users is adjustable based on whatever assumptions you'd like to make. If a user uses the 'logout' function in the LMS, the LMS session goes away immediately, but if they merely kill their browser or shut down without logging out, they will appear to still be logged in, apparently indefinitely. Anyway, here's the SQL:
SELECT *FROM TBL_User
WHERE (LoggedIn = 1) AND (LastLoginDate > DATEADD([day], - 1, GETDATE()))
This assumes anyone who logged in more than a day ago is 'stale' rather than a current user. Now of course, getting this into the system in some way you can execute it is the trick to solve. If the necessary columns are exposed to ReportManager, that may be an option. I haven't played with ReportManager enough to know that.
--
Joe Kyle
--jjkd--
See active (logged in) users
Ok, I was able to get this basic data using ReportManager. I had to add a datasource for the production database (as looking in the replicated data would be fairly meaningless), and that worked for getting at the appropriate table. Filtering out based on the value of
LoggedInwas easy, though I haven't figured out how to set up the filter for 'stale' data.--
Joe Kyle
--jjkd--
See active (logged in) users
Hi Reading the above comments, does 7.X still use the same behaviour as Docent in terms of keeping sessions active after someonehas closed their IE window?
See active (logged in) users
Yes, I have tested this with 7.2, the TotalLMS system doesn't notice when the user leaves 'ungracefully' --- closed browser, dropped network connection and so forth. The logged in status seems to persist in the database indefinitely.
Now, IIS/ASP seems to be able to track this somewhat better, using the performance monitor will show that the ASP session is dropped when the browser window closes. I haven't checked to see what happens or how long it takes/if IIS/ASP will time those out at some point, but I'd imagine it would.
--
Joe Kyle
--jjkd--