Discuss and solve problems in energy management and automation. Join conversations and share insights on products and solutions. Co-innovate and collaborate with a global network of peers.Register Now
>>Message imported from previous forum - Category:ClearSCADA Software<<
User: rlao, originally posted: 2019-11-14 04:41:37 Id:627
Is there something in ClearSCADA to terminate a WebX client session after it has been open for too long?
Our users have a habit of leaving WebX open in the background and then not shutting down IE after they've left work for the day. The WebX session then stays open for several days using up a licence.
Having the ability to do something like kill WebX sessions after 24 hours of uptime and force them to reload the session would be useful to reduce occurrences of this.
Solved! Go to Solution.
>>Responses imported from previous forum
Reply From User: adamwoodland, posted: 2019-11-14 05:34:19
Which WebX? DBServer hosted or IIS hosted?
With DBServer hosted WebX there was a trick to add a meta HTML tag to each page that after a certain time period (12 hours in your case) it would redirect them to Google.
Haven't looked into it for WebX hosted. Maybe IIS itself has something.
Reply From User: rlao, posted: 2019-11-17 23:06:11
DBServer hosted. I'm interested in this little trick Adam, care to share? 😉
Reply From User: adamwoodland, posted: 2019-11-18 07:32:02
Sure, if you keep that water flowing to my house! They have made this easy in recent versions...
On the server go to "C:\\Program Files\\Schneider Electric\\ClearSCADA\\WWW\\XSL" and backup "common.xsl"
Open common.xsl, at the top look for:
It won't look exactly like that, the refreshURL will be blank. But set it to something like the above and after x seconds (120 in my case) it will redirect to Google. Each time you view a new page the counter restarts...
Reply From User: adamwoodland, posted: 2019-11-18 23:23:16
Also watch out for client-side caching with those xsl, I had to reopen IE to test it properly.
The common.xsl snippet in Adam's original response didn't make it through the import.
Looks like code snippets aren't properly supported yet as I'm unable to copy the XML with the element brackets without throwing up an error. However, I can disguise it as plaintext.
In common.xsl, you should be looking for:
xsl:param name="refresh" select="120"
xsl:param name="refreshUrl" select ="'https://www.google.com'"