Siebel Server Administration Guide > Siebel Server Infrastructure Administration >

Configuring Session Manager

Session Manager is a layer in the Siebel Web Server Extension (SWSE) that manages TCP/IP (SISNAPI) connections between Web servers and Siebel Servers. (SISNAPI is a Siebel-proprietary communication protocol between the Web server and the Siebel Server; the acronym stands for Siebel Internet Session API (Application Program Interface)). Session Manager funnels multiple client connections from the Web server to the Siebel Server through a single connection. By using Session Manager, network sessions can be multiplexed through fewer SISNAPI connections.

NOTE:  Resonate Central Dispatch must be used to load balance interactive mode server components across Siebel Servers in a multiple Siebel Server environment. For more information about implementing Resonate Central Dispatch, see the Siebel Server Installation Guide for the operating system you are using.

When a client requests a new session, the SWSE receives the HTTP request from the Web server, translates the request into SISNAPI messaging format, and invokes Session Manager to obtain a physical connection to the Siebel Server. Session Manager creates a new, temporary SISNAPI connection, which is load-balanced to an available Siebel Server. After this temporary connection is made to a Siebel Server, Session Manager checks to see if there is open, existing SISNAPI connection between the local Web server and this Siebel Server. If a connection is found with room available for a new session, then the temporary connection is dropped and the existing connection is used for this new user session. If a connection is not available, then the temporary connection is retained. (Each physical connection can accommodate multiple user sessions.) The parameter Number of Sessions per SISNAPI Connection (alias SessPerSisnConn) controls the maximum number of sessions allotted on each connection to the Siebel Server and, indirectly, the number of open connections.

After Session Manager opens a connection to the Siebel Server, connections are closed based on the time the connection remains idle. The parameter SISNAPI Connection Maximum Idle Time (alias ConnIdleTime) controls this feature. Upon reaching the configured idle period, the connection is disconnected by the Application Object Manager process. An additional benefit of this parameter is to manage connections that pass through a firewall placed between the Web server and the Siebel Server. As firewalls block idle connections, the ConnIdleTime parameter can be configured to disconnect idle connections before they are blocked by the firewall. This setting avoids future connection problems between the Web server and the Siebel Server.

NOTE:  Only enable the parameter SISNAPI Connection Maximum Idle Time at the component level, specifically, for Application Object Manager components.

For further details on communication between the client and the Siebel application, see Web Client Communication with Application Object Managers.

Parameters that modify Session Manager and SISNAPI connections are available for each component at the component level. For details on these and other parameters, see Parameters. For information on modifying component parameters, see Administering Component Parameters.


 Siebel Server Administration Guide 
 Published: 23 June 2003