Optimizing WebLogic Server Parameters

Scenario:

If the following conditions apply to your environment, then check the WebLogic Server settings described in the Solution.

Your application's performance is slow.
You have tried the solutions in Optimizing Performance.
Your application uses WebLogic Server.

Solution:

To tune WebLogic Server performance settings:

Open the WebLogic Server Administration Console.
Select the deployed Oracle Hyperion Planning application, the Configuration tab, the Tuning tab, and then set these values:
- Servlet Reload Check: -1
  
  This option sets the number of seconds that WebLogic Server waits to check whether a servlet was modified and needs to be reloaded. The value -1 means to never check.
- Resource Reload Check: -1
  
  This option sets the number of seconds that WebLogic Server waits to check whether a resource was modified and needs to be reloaded.
- JSP Page Check: -1
  
  This option sets the number of seconds that WebLogic Server waits to check whether JSP files have changed and needs to be recompiled.
Open the properties of the server, select the Tuning tab, and then select Enable Native IO.

Selecting this option ensures that WebLogic Server uses native performance packs. By default, when you are in Production mode, using native performance packs is enabled in config.xml.
To turn off HTTP access logging, open the server properties, select the Logging tab, the HTTP tab, and then clear HTTP access log file enabled.

By default, WebLogic Server enables HTTP access logging. Because the Web Server already creates an HTTP access log, this step turns it off.

Caution:

HTTP access log files grow proportionally with the number of requests. If you do not configure log rotation properly, the access log file can grow very large and potentially fill up the disk, causing the application and the operating system to stop working. When this condition occurs, to remove the log files, you must stop and then restart the application server.