How To Reduce Memory Consumption Of The Siebel Swse Plugin On Unix Platforms
(Doc ID 1427293.1)
Last updated on JANUARY 09, 2020
Applies to:Siebel CRM - Version 8.2.2 SIA and later
IBM AIX on POWER Systems (64-bit)
Oracle Solaris on SPARC (64-bit)
A new functionality has been recently introduced that allows to run the Siebel web server plugin with reduced memory footprint.
This note will explain how the Siebel web server plugin can be modified in order to allow the session manager to establish more sisnapi threads per web server process.
This note applies only to the following Fixpacks:
18.104.22.168 and above
8.2.2 and above
See also the 8.2 Siebel Performance Tuning Guide.
This note is only applicable when you run a Web server on a Unix flavor platform.
The Session Manager is a layer within the Siebel Web Server Extension (SWSE) and Application Object Manager (AOM) that manages TCP/IP (SISNAPI) connections between clients to AOMs.
See also Bookshelf, Siebel System Administration Guide > Configuring the System Architecture > Configuring Session Manager
A sisnapi thread is a thread in the Siebel web server plugin that establishes the connection between the web server and the SCBroker listening port on any application server node.
Since a web server requires at least one thread per AOM process running on any application server node, the number of these threads can be quite high.
In a typical setup with 100 tasks per AOM process you would have 5 sisnapi threads per process.
This value needs to be multiplied with the value of maxmtservers and the number of server nodes to get an estimate about the maximum number of sisnapi threads running in a web server process.
See also Bookshelf
You might benefit from the new functionality when you expect more than 1000 concurrent sisnapi threads per web server process.
The number of established sisnapi threads per web server can be verified by running the command
netstat -a | grep 2321
on your web server, where 2321 is the default SCBroker port number.
Each established network connection corresponds to 1 thread in the web server process.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document