1. Configuring Siebel Open UI Guide
  2. Configuring the Portlet Session to Stay Alive

Configuring the Portlet Session to Stay Alive

Siebel sessions that are not in use will eventually expire. The time for which the session is kept alive is determined by the value of the SessionTimeout server parameter. In some cases when exposing Siebel CRM as a portlet expiring sessions this might not be optimal.

To override the SessionTimeout server parameter so that the portlet session stays alive, include the following attribute in the URL:

KeepAlive=1

[Other values for this parameter are as follows: TRUE, T, ON, and Y.]

The full URL should use the conventions in the following example: 

http://<siebel_server>/<siebel/app/application>/lang?IsPortlet 
=1&SWECmd=GotoView&SWEView=Contact+List+View&KeepAlive=1

When using the KeepAlive attribute, consider these additional guidelines:

  • The KeepAlive attribute value is enforced by monitoring periodic client pings to the Siebel Server. Consequently, the client must be on a network connected to the server.

  • If the KeepAlive attribute value is omitted or set to FALSE the session will eventually timeout and a login screen is returned to the portlet.

  • Once the KeepAlive attribute is set to TRUE by a request (either the URL or a subsequent message-based communication) it cannot be changed to FALSE by a subsequent request.