Enabling Siebel Thin Client
This section describes the requirements for Siebel 6.2.1 to work with Microsoft BizTalk Adapter for Siebel eBusiness Applications. Siebel 6.2.1 requires that you enable the Siebel Thin Client Enterprise Component to enable any thin client to communicate remotely with the Siebel Application Server.
Follow these steps to verify that the Siebel Thin Client Enterprise is enabled on the server.To verify the Siebel Thin Client Enterprise is enabled
Log on using the Siebel Client (with Server Administration enabled).
The user ID must have sufficient authorization to make server management changes.
Select Screens, point to Server Administration, point to Enterprise Configuration, and then click Enterprise Component Groups.
Make sure that the Thin Client component is enabled.
If it is not enabled, check the component in the list, and then click Enable.
Restart the server to make sure that the settings are registered and the component is started.
The following settings can help memory management when you use a thin client extensively in BizTalk Adapter for Siebel eBusiness Applications multithreaded or multiuser scenario.
Setting Max Tasks and Max MT Server Parameters
The following is a guideline for setting certain parameter values for the Siebel Object Manager (SOM) components.
FAQ 1380 from Siebel Support - The SOM is primarily used for thin client connections. The SOM is like a connected client that makes requests for multiple users. The SOM caches information in several different ways. Some information is cached and used by all connections, and other information is stored for each user connection. Using SOMs is more efficient than using connected clients because up to 20 thin client connections can use one SOM. The clients processing power and memory requirements can be reduced significantly, whereas the server requirements go up.
There are some concerns with memory growth for the SOM processes. Siebel has implemented some parameters to clean up the memory used by SOM.
How the Mechanism Works
There is a parameter called the RecycleFactor, which multiplies the maximum number of threads that a multithreaded server can run at the same time (it works together with the MaxMTServers and MaxTasks parameters). When the RecycleFactor is set to n, it causes the current Object Manager processes to shut down and a new Object Manager to start every n number of connections.
When the multithreaded server is started, it calculates how many threads it can run before it has to recycle itself using the following formula:
(MaxTasks / MaxMTServers) * RecycleFactor
|Remember to always make MaxTasks divisible by MaxMTServers.|
When a task is created for a client connection, the multithreaded server verifies whether it is time for recycling; if it is, the server stops accepting more client connections (starting new tasks) and creates a new multithreaded server to handle new connections. When the last task ends in a deactivated multithreaded server, the process exits.
This functionality applies to situations where a server component might be leaking any kind of resource. For example, a user may want to recycle the process (multithreaded server) when it has serviced 20 clients. That means that it can run 20 tasks before it must recycle. On the other hand, because of concurrency limitations, only 20 tasks can be run per process (multithreaded server), and users want to be able to handle up to 1000 simultaneous tasks. The values for the configuration parameters will be:
MaxTasks = 1000 MaxMTServers = 50 MinMTServers = Max MTServers = 50 RecycleFactor = 1
These values provide the following:
Concurrent tasks per server = MaxTasks / MaxMTServers or 1000 / 50 = 20
The recommended ratio of MaxTasks to MaxMTServers is 20 to 1. Higher ratios, such as 25 to 1 or 30 to 1, cause a high number of context switches to occur resulting in poor performance. Low ratios, such as 10 to 1 or 5 to 1, do not take advantage of the architecture for high scalability.
Max tasks before recycling = concurrent tasks per server * RecycleFactor or 20 * 1 = 20
The RecycleFactor is a hidden parameter. You must set it using the command line server admin tool (srvrmgr).
Use the following command at the srvrmgr prompt:
change param RecycleFactor= 3 for comp <component_name> server <server_name>
The default value for this parameter is 0 (zero), which means never recycle. The value of the RecycleFactor must be greater than 0 (zero) if Resonate is used.
Setting Maximum MT Servers and Minimum MT Servers
On the Siebel menu, point to Screens, point to Server Administration, point to Enterprise Configuration, and then click Enterprise Parameters.
Setting Maximum Tasks
On the Siebel menu, point to Screens, point to Server Administration, point to Tasks, and then click Task Parameters.
The thread pooling component parameters are MinPoolThreads, MaxPoolThreads, and UseThreadPool.
MaxTasks / Max MT Servers = Number of sessions per Object Manager