Performance Tuning Guide > Tuning Operating Systems for Performance > Tuning Siebel Business Applications for Solaris >

Tuning the Sun Java System Web Server for Solaris

If you have a busy Web server, some of your users might experience difficulty connecting to your Web server. To address this issue, change the tcp_conn_req_max_q and tcp_conn_req_max_q0 default values, using the ndd command. For details on how to use the ndd command, see Tuning AOM Instances for Solaris.

NOTE:  To avoid losing the new settings when the machine is rebooted, add them to /etc/init.d.

You also should tune the Sun Java System Web Server for optimal performance using the following procedure.

To tune the Sun Java System Web Server

1. Using a text editor such as vi, open the file Webserver_Root/config/magnus.conf, where Webserver_Root is the root path of the Sun Java System Web Server.
2. Set the parameter RqThrottle to 1200.

   The RqThrottle parameter specifies the maximum number of simultaneous transactions the Web server can handle. The default value is 512. By changing this value to 1024, you can minimize latencies for the transactions that are performed.

3. Add or modify the MaxKeepAliveConnections parameter, setting its value to 1000. The default value is 200.
4. Save your modifications to the magnus.conf file.
5. Restart the Web server.

   After making the changes above to the Sun Java System Web Server parameters, change the following parameters on the workstation hosting the Sun Java System Web Server.

6. Open the /etc/system file for editing.
7. Set the following Solaris system parameters:

   Parameter	Scope	Default Value	Tuned Value	Comments
   rlim_fd_max	/etc/system	1024	8192	Process open file descriptors limit; should account for the expected load (for the associated sockets, files, and pipes, if any).
   rlim_fd_cur	/etc/system	64	8192

8. Restart the workstation hosting the Sun Java System Web Server.