When ever you deploy a new WebSphere Portal instance you must tune the Portal appropriate to the environment. For example, out of the box, Portal is NOT tuned for production.
The IBM Portal Performance team has produced several documents that contain the tuning that should be done after installation and before deploying a Portal to production. This is the document for V7 and this is the one for V8. This document should be considered a prerequisite for the beginning of performance testing and certainly a prerequiste for production.
There are several components that should be tuned. These include the Portal itself, the LDAP, the database, the OS and the web server.
Mike White and I have written a ConfigEngine script that will apply the tunings for the Portal automatically. The script is included in Portal V184.108.40.206 CF22, Portal V8 CF05 and all levels of 8.5. Use of this script will improve the accuracy of applying the tuning changes as well as reduce the time needed to do the task.
The changes are driven by a properties file (tuning.properties) along with several resource environment providers files. Since the tuning.properties file assume you are a WCM rendering server that is only a subscriber (and NOT a syndicator), you may need to adjust some of the setting to match your environment. You can easily do this by copying the read-only tuning.properties to a local directory, updating the name/value pairs that need updating and point to the new copy when you run the task.
Note for zOS users: This task does run on zOS. Note however, that there were significant fixes put into the code to resolve zOS issues in March, 2014. These fixes wil be included in 8001, CF10 as well as the initial release of V8.5. If you are on zOS and not running at least 8001 CF10 level, please download the linked code immediately following.
The latest README file is linked here. It provides the details on using this new task. I have also included the (current) latest version of the code here. The latest version can be untarred in the PortalServer/installer/wp.config/config subdirectory as is. Note that the default the subdirectory just mentioned does NOT have write permission. The permission must be changed before trying to untar this file.
Please Note: These defaults in the tuning.properties file assume the server being tuned is a WCM rendering server that is NOT subscriber only. It will also set the WCM advanced cache. If you are running this on an authoring server, you should consider turning off WCM advanced caching.