IBM 6.1.X manual Database Tuning, Database name, Datasource name

Database Tuning

D A T A S O U R C E T U N I N G F O R D B 2

Multiple databases are used to hold information in WebSphere Portal V6.1. We used six separate DB2 databases, each representing a separate database domain and having their own datasources. These are:

Table 7: DB2 Database Domains

Database	Database name	Datasource name
Release	release	reldbDS
Community	community	commdbDS
Customization	custom	cusdbDS
Feedback	fdbkdb	fdbkdbDS
Likeminds	Lmdb	lmdbDS
JCR	jcrdb	jcrdbDS

All datasources are configured in a similar manner by logging on to the WebSphere Application Server administrative console. For the prepared statement cache size, the path is Resources → JDBC Providers → provider name → Data Sources → datasource name. The provider name and datasource name are based on the names selected for that database during the database transfer step. Look for the parameter Statement cache size.

For the connection pool settings, the path in the WebSphere Application Server administrative console is Resources → JDBC Providers → Provider name → Data Sources

→Datasource name → Connection Pools. The settings are Minimum connections and Maximum connections.

The default settings were used for the prepared statement cache size, and connection pool minimum and maximum sizes.

D B 2 D A T A B A S E S E R V E R T U N I N G

WebSphere Portal V6.1 uses database servers for core functionality. In our measurement environment, we used DB2 database server for the Portal application. The LDAP server, IBM Tivoli Directory Server also included a DB2 database as a repository, but it is largely unseen and was operated as an out of box configuration.

We recommend using a remote database server for the largest capacity. For our measurements we used IBM DB2 Enterprise Edition V9.1 fixpack 5 as our database server. WebSphere Portal V6.1 uses the concept of Database domains to designate either groups of tables belonging to one domain, or even entirely separate databases to store the data specific to each domain.

1 5

W E BS P HE R E P O R T AL V 6 . 1 T U N I N G G U I D E