httpSessionTimeout setting - your experience?

[whchuang]

Dear all,

This topic is related to this (system time-out causing learning completion to be lost), which is bothering our company recently. We have a 2-hour long eLearning SCORM course which we experienced a lot of users reported "course completion" related issues. We are considering to change the httpSessionTimeout setting (at both LMS and BizX levels) to either 2 hours or 8 hours (max allowable by SAP I believe). Just want to know if anyone here have any success stories to share by changing this httpSessionTimeout setting, and if changing this particular setting would create any known unexpected undesired system behavior (other than non-users potentially can go into LMS and obtain confidential information from within LMS, as that should be relatively low risk for us). Thanks!

[whchuang]

By the way, I was very surprised to find out that according to SAP KBA 2088893, "BizX suite has a hard default setting of 30 minutes timeout on no activity" and we can not change it. This is crazy as we were told by another SAP Support Engineer that if we want to change the Session TimeOut setting (see SAP KBA 2316953) , we will need to change this setting on both LMS and BizX sides. However, in this case the BizX session timeout setting can NOT be changed (it almost feel like that 30 minutes had been "hard-coded"). This is really not acceptable as other LMS systems (such as Moodle "increase session timeout" and CSOD) can easily change the http session timeout to longer than 4 hours etc. Can SAP do something about this please?

There are also two "enhancement requests" about this (#263029 and #284402), which I urge everyone to vote for them if you are experiencing the same issue. Thanks!

[PKetnouvong]

This would be an instructional design issue with the course. The course should send back information every 7-10 minutes to tell the LMS that the session is still active.

We have 1 hour long recorded webinars that we break up into 5-6 minute segments and moves from segment to segment automatically. The user thinks it's one full video but the system sees it as segments. As it moves from segment to segment, the course sends bookmarking info to the LMS. This keeps the session alive.

In other courses that need the user to click next (send bookmarking), we tell users to not push the course aside while multi-tasking. It will cause the system to timeout because they are not actively engaged in the course.