Siebel Session Time-out – White-listing Your Message Bar

White-listing what?

In my recent post discussing the merits of Innovation Pack 15.2 / 14.8 I pointed out the new feature which would allow sessions to time-out regardless whether the message bar functionality is enabled or not. Traditionally when enabling the message bar in Siebel, a Siebel session would hardly time-out (depending whether the SessionTimeout value in the eapps.cfg would exceed the value of the object manager’s MessageBarUpdateInterval parameter. This latter scenario is typically the case.

Further, the High Interactivity client would gracefully close a Siebel session either if the user would explicitly log-out or use the infamous browser’s ‘X’ button. Important, because otherwise the message bar polling would keep the session alive.


However… with Open UI we have absolutely no means to capture the ‘X’ event. Period. That means, if you’d enable the message bar functionality (or rather “Notifications” as we call them in Open UI, because the message bar as such has gone) and a user would hit ‘X’ the Siebel session would remain a living thing. Killing those orphaned sessions would be an administrator job. Ugly.

So with patch set IP15.2/14.8 an important feature got introduced:

Siebel Session Time-Out Application Method White-listing

A feature with a generic nature, configurable through the eapps.cfg. White-listing as such that certain configured application methods would not reset the time-out counter.

Just add this parameter to your eapps.cfg in the [defaults] section, or override if you like on a specific virtual directory instead:

SessionTimeoutWLMethod = UpdatePrefMsg

The value could be a  comma-separated list, to allow other (future) methods as well to be white-listed. If you ask me, quite an important feature. Why? Because with the introduction of the appealing “Notifications” feature in Open UI, the inherent problem allows orphaned sessions on the Siebel Servers easily to start piling up ridiculously fast. Train the users to log-out? You can try. But when was the last time you logged-out of any web application…? User’s are simply not doing this, how hard you try to train & explain.

– Jeroen

PS: I’m on holidays starting today – so I will be offline 🙂


5 thoughts on “Siebel Session Time-out – White-listing Your Message Bar

  1. Hi Jeroen,

    according to my tests on using Open UI a session which has been “closed” by closing the browser window (without explicit Logout) still times out after the SessionTimeout value set in eapps.cfg, even if the CFGMsgBarUpdateInterval is less then the SessionTimeout.
    In our production environment we have set SessionTimeout=180 and CFGMsgBarUpdateInterval to 120, which results in no sessions timing out as long as the browser windows is open (this was the business requirement) but the session is gracefully closed after 3 minutes after the user has closed the browser tab or windows and thus also saving any changed user preferences in the .spf file.
    The drawback of course is some memory overhead for the “unused” (but still open) sessions in the Object Managers, but more happy users who don’t have to re-login after a session timeout.

    Kind regards
    Werner Dietrich
    (former Principal Architecture Specialist @Siebel Expert Services)

  2. Hi,

    also very important to add this method GetAlarms to the white list:

    For Example, SessionTimeoutWLMethod = UpdatePrefMsg, GetAlarms

    Jose Luis

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s