IBM WEBSPHERE 6.1.X User Manual
Page 46
4 1
W E B S P H E R E P O R T A L V 6 . 1 T U N I N G G U I D E
Z / O S
The following section details the tunings that we made in our DB2 9 for z/OS backend
database during our testing. To start here are a few general recommendations:
•
When the DB2 z/OS server is on a different server to the Portal/WCM installation, the
use of the Universal Driver type 4 database driver is recommended
•
For data sharing groups, we additionally recommend enabling Sysplex Distributor to
enhance high availability and exploit workload balancing.
In our environment we created nine databases to support WCM on Portal. The release,
customization, community, likeminds, and feedback are required for Portal. For WCM, a
minimum of two JCR databases are required for scalability and in our environment we used
four.
T A B L E S P A C E S
Following DB2 best practices, it is recommended to create all tables into individual
tablespaces. This will avoid device contention and provides better monitoring possibilities.
Furthermore, most DB2 utilities such as REORG operate with tablespaces rather than
tables.
B U F F E R P O O L S
It is also beneficial to create separate bufferpools for use by Portal to avoid contention.
When creating your database, ensure that each tablespace/indexspace has a specific
bufferpool specified by the BUFFERPOOL/INDEXBP attributes rather than using the DB2
system defaults. It is recommended that a set of bufferpools separate from the Portal
databases gets created for the JCR databases. The following table shows the settings for
our configuration.
Table 23: DB2 z/OS Bufferpool Settings
Bufferpool settings
Database Domain
wkplc_comp.properties
DB2
BP
BP
Pagesize
(KB)
BP
Size
BP2
4
40000
BP3
4
5000
RELEASE
CUSTOMIZATION
COMMUNITY
LIKEMINDS
FEEDBACK
BP32K
32
1000
jcr.Db4KBufferPoolName
BP4
4
80000
jcr.DbIndex4KBufferPoolName
BP5
4
40000
JCR
jcr.Db32KBufferPoolName
BP32K1
32
20000
Note: When running Portal, DB2 objects like tablespaces will be created dynamically. It is
important to keep your default bufferpools well defined to avoid causing contention due to an
overloaded bufferpool. This is especially true for LOB and 4-KB tablespaces as they default