Introduction: Looking for a resource center to tune Websphere®portal Web Content Management and Ibm®db2®for linux®, UNIX®, and Windows® environments? This article describes the unique parts of the environment that require special consideration. You will learn how to tune application Server and WebSphere Portal. As a good start, you will learn about the various registry variables and database Manager and database configuration parameters that should be set to the specified value. Finally, the ongoing Maintenance section provides guidelines on how to make the DB2 system continue to function efficiently as the system grows.
Performance tuning of the environment
The tuning of the WebSphere Portal environment involves tuning and configuring different systems and components for the environment. This section discusses common concepts and describes in detail the characteristics of the configuration that this article uses to evaluate the environment. The configuration and tuning of the WebSphere Portal Web Content Management (WCM) AIX®POWER4 evaluation environment is based on the WebSphere Portal AIX Power4 Environment, IBM WebSphere Por Tal Version 6.0 Tuning Guide A detailed description of the latter. All the differences in the environment used to evaluate WCM are clearly presented in this chapter. The complete tuning and configuration methods for any WebSphere Portal environment include:
Configure the application server and the resources defined for this application server
Identify replication policies for extending the environment
Tuning database and database servers
Tuning the directory server and its databases
Tuning your Web server
Tuning operating systems and networks
Tuning the WebSphere Portal service
When tuning systems, you should first have a baseline and monitor performance metrics to determine if a parameter should be changed, and when making changes, monitor the performance metrics to determine the effect of the change.
Understanding the Environment
The WebSphere Portal V6.0 uses an additional server to provide its functionality. In my evaluation environment, in addition to the portal server itself, there is a WEB server, a database server, and a directory server that is placed on a separate system outside of the WebSphere portal system. The primary benefit of this configuration is that you can avoid competing resources between multiple servers on the same system. If other servers compete for resources with the WebSphere Portal server, the throughput rate that the system can reach is affected. In this report, the configuration used for profiling puts IBM HTTP Server on the same system as the WebSphere Portal.