Tuning Siebel Business Applications for AIX

This topic provides instructions for configuring and tuning operating system settings and Siebel Enterprise Server components so that you can run Siebel applications on AIX. It contains the following information:

"Tuning the Siebel Server for AIX"
"Tuning Kernel Settings for AIX"

Tuning the Siebel Server for AIX

This topic is part of "Tuning Siebel Business Applications for AIX".

AIX provides several environment variables that can be tuned to optimize Siebel Server performance. These environment variables and their values are used as start parameters when the Siebel Server is started. Table 13-1 and Table 13-2 describe each of these environment variables and their recommended settings.

Note:

For more information about tuning the Siebel Server, see "Tuning the Siebel Server for All UNIX and Linux Operating Systems".

Table 13-1 Environment Variables Used for Optimization in $SIEBEL_ROOT/siebenv

Environment Variable	Value	Description
AIXTHREAD_SCOPE	S	Controls contention scope. S signifies system-based contention scope (1:1).
AIXTHREAD_MNRATIO	1:1	Controls the M:N ratio of number of kernel threads that must be employed to handle runnable pthreads.
AIXTHREAD_MUTEX_DEBUG	OFF	Maintains a list of active mutexes for use by the debugger.
AIXTHREAD_RWLOCK_DEBUG	OFF	Maintains a list of read-write locks for use by the debugger.
AIXTHREAD_COND_DEBUG	OFF	Maintains a list of condition variables for use by the debugger.

Table 13-2 Environment Variables Used for Optimization in $SIEBEL_ROOT/bin/siebmtshw

Environment Variable	Value	Description
SPINLOOPTIME	1000	Controls the number of times to retry a busy lock before yielding to another processor.
YIELDLOOPTIME	>=n A number greater than or equal to the number of processors.	Controls the number of times to yield the processor before blocking on a busy lock (only for libpthreads). Set this variable, at the minimum, equal to the number of processors on the computer.
MALLOCOPTIONS	buckets,considersize,multiheap:4	Include in the value an integer representing the number of processors on this computer. In this case, the value 4 would be used for a four-processor computer.
LDR_CNTRL	Example values: `LOADPUBLIC@MAXDATA=0x50000000` (this value, which specifies five segments, sets a maximum process size of 1.25 GB) `LOADPUBLIC@MAXDATA=0x60000000` (this value, which specifies six segments, sets a maximum process size of 1.5 GB)	The `LOADPUBLIC` option directs the system loader to load all modules requested by an application into the global shared library segment. Set `LDR_CNTRL` in the environment of the user, or, preferably, in the shell script that launches the executable program that needs the extra memory.

Tuning Kernel Settings for AIX

This topic is part of "Tuning Siebel Business Applications for AIX".

There are several AIX kernel settings that you can tune for optimal Siebel Server or Siebel Application Interface performance under AIX. These include the Virtual Memory Management and TCP settings. You must have root privileges to modify these settings. Use the vmo, ioo, and no commands to tune the AIX kernel. For more information about AIX kernel settings, including several that are not mentioned in this guide, see 1097858.1 (Article ID) on My Oracle Support. See also your operating system vendor's documentation.

To change the kernel settings

Using a text editor such as vi, open the /etc/rc.net file for editing.
Modify settings using ioo and no, following the guidance of 1097858.1 (Article ID) on My Oracle Support.

Note:
Use default values for settings for vmo.
Check the settings for all User Limits (ulimit) and make sure that they are set to -1 (unlimited), as follows:
```
ulimit if -a
```
Note:
To change the set limits, update the /etc/security/limits file by changing all ulimit parameter values to -1 (unlimited).
Save your changes and exit the editor.
Make sure that the rpc.statd and rpc.lockd daemons run on the Siebel Server computer and on the server computer where the Siebel File System is located. Then set the number of threads for the rpc.lockd daemon on each applicable server computer.

It is recommended to increase the number of rpc.lockd daemon threads from the default. If possible, use the maximum number of threads, which is 511. System degradation can occur and logins might be blocked if the rpc.lockd daemon is not configured to handle a large number of lock requests. For example, you might execute commands like this:
```
chssys -s rpc.lockd -a 511stopsrc -s rpc.lockd; startsrc -s rpc.lockd
```
Restart the server computer to have the new settings take effect.