IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
Kernel settings for Solaris on WAS
Several Solaris kernel values are typically too small for IBM WAS.
To adjust the kernel values:
- Before installing, review the server configuration:
sysdef -iThe kernel values are set in the /etc/system file, as shown in the following example.
set shmsys:shminfo_shmmax = 4294967295 set shmsys:shminfo_shmmni = 1024 set semsys:seminfo_semmni = 1024 set semsys:seminfo_semmsl = 100 set semsys:seminfo_semopm = 100 set rlim_fd_cur=1024- Change kernel values by editing the /etc/system file then rebooting the operating system.
For more information about setting up the Solaris system, see the Solaris System Administration documentation at the following Web site:http://docs.sun.com/app/docs/prod/solaris.admin.misc
For example, the Solaris Tunable Parameters Reference Manual at the following Web site: http://docs.sun.com/app/docs/doc/816-7137?q=shmsys
Queue managers are generally independent of each other. Therefore system kernel parameters, for example shmmni and semmni, need to allow for the number of queue managers in the system.
All the other kernel tunable parameters that the installation and configuration Guide recommends to adjust are in the System V IPC (Interprocess Communication) tunables. In Solaris 10 all System V IPC facilities are either automatically configured or can be controlled by resource controls.
The following parameters are still operational but use of the corresponding resource controls is recommended.
msgsys:msginfo_msgmnb - process.max-msg-qbytes msgsys:msginfo_msgtql - process.max-msg-messages semsys:seminfo_semopm - process.max-sem-ops semsys:seminfo_semmsl - process.max-sem-nsems shmsys:shminfo_shmmax - project.max-shm-memory shmsys:shminfo_shmmni - project.max-shm-ids msgsys:msginfo_msgmni - project.max-msg-ids semsys:seminfo_semmni - project.max-sem-idsObsolete parameters can still be included in the /etc/system file on a Solaris 10 system. If this is the case the parameters are used to initialize the default resource control values used in previous Solaris releases. You can override these by setting the corresponding resource controls. An important distinction between the obsolete IPC tunables and resource controls is that the IPC tunables were set on a system-wide basis and the resource controls are set on a per-project or per-process basis allowing for a more flexible tuning of different workloads in the system.
Parent topic:
HP-UX and Solaris: kernel settings for WAS