16
WEBSPHERE PORTAL V6.1 TUNING GUIDE
We built six separate databases within one database server to house the tables and data
needed to support each domain. For the Base Portal and Many Pages measurements, the
Release domain is the primary database being exercised.
The databases and related domains supported by Portal V6.1 are:
1. Release (release domain). This is the primary database domain used by the Base
Portal and Many Pages Scenarios.
2. Customization (customization domain). This database receives some light traffic in
our scenarios.
3. Community (community domain). This database receives some light traffic in our
scenarios.
4. JCR (JCR domain). JCR database is used heavily in WCM (Web Content
Management) Scenario. This database receives light traffic in all other scenarios
measured in our Benchmark report.
5. Likeminds database, used for Likeminds enabled systems. This database is not used
in the scenarios measured in our Benchmark report.
6. Feedback database, used by the feedback subsystem. This database is not used in
the scenarios measured in this report.
DB2 ON AI X SETUP
We configure our DB2 database on AIX using the following setup,
• Set the filesystem which will hold the Portal databases to be a Enhanced
Journal File System (JFS2) because a large file system is limited to 64GB.
• Turn on concurrent I/O (CIO) for Enhanced Journal File System as this improves
performance.
To enable CIO, use the following command to mount the database fileset.
Mount –o cio /portaldb
• Increase AIX maximum number of processes per user to 4096.
The default 500 processes per user is too low for database server, we increase
it to 4096 in our AIX environment. To increase it,
chdev –l sys0 –a maxuproc=’4096’