Database Administration Guide

Using a DB2 Database

This section describes the steps necessary to use a DB2 database with WebLogic Portal 8.1, and includes information on the following subjects:

Typically, the steps in this chapter should be performed by a database administrator.

Note: Review this entire chapter and any release notes before proceeding.

Configuring a DB2 Database

Before proceeding, be sure you have read Overview of Database Configuration for WebLogic Portal on page 1-1.

Install the DB2 client software and configure it to connect to the target DB2 database. See your DB2 documentation for more information.

Verify that you can connect to the target database through the Command Line Processor (CLP).

Prepare the DB2 database. The database creation scripts will install domain-specific tables for each. It is recommended that you work with a database administrator to adjust the SAMPLE scripts, and to create the database objects (users, passwords, tablespaces, etc.) needed for your environment.

Notes: Multiple databases are required if you have multiple domains, or to run multiple environments using the same DB2 instance (for example, if you want to run development and system test from a single DB2 installation).

Be sure to back up your database schemas before installing any new database objects. See your database documentation for details.

DB2 Configuration Parameters Minimum Settings for DB2

To ensure the Portal application can successfully run on DB2 there are some minimum configuration parameters that need to be set. Without the minimum settings, heavy Portal activity may exceed database capacity.

Configure you DB2 database with the following configure parameter as guidelines for minimums:

Dynamic Sections:20,000
applheapsz: 24,000
pckcachesz: 2500

Review and modify the provided sample scripts to suit your environment. The scripts are located in <WL_HOME>/portal/db/db/db2/8/admin.

The following table lists the script names and the usage notes for each script.

Script Name

Description

create_user.sql

Grant createtab, bindadd and connect DB2 privileges to the WEBLOGIC schema owner user.

Usage Notes: Because IBM DB2 databases authenticate users via the operating system (OS), you need to create an OS user that will own database schema objects. Edits are required to change the schema owner user name.

The default schema owner user name and password are the following:

schema owner user: WEBLOGIC

schema owner user password: WEBLOGIC

create_bufferpool.sql

Create an 8K bufferpool, if one does not already exist.

Usage Notes: DB2 must be stopped and restarted to utilize new bufferpools. Edits are required to change the 8K bufferpool name.

The default bufferpool is BP8K.

create_tablespaces.sql

Creates a 4K and 8K regular tablespaces.

The default tablespace names are the following:

WEBLOGIC_DATA_4K: Tables for WebLogic Portal and/or WebLogic Platform with rowsize smaller than 4K.

WEBLOGIC_DATA_8K: Tables for WebLogic Portal and/or WebLogic Platform with rowsize larger than 4K and smaller than 8K.

Usage Notes: Edits are required to specify valid physical disk locations for your environment (d:\db2\data\data4k), for a database user other than WEBLOGIC and to change buffer pool names.

create_temp_tablespaces.sql

Create an 8K temporary tablespace.

The default tablespace name is TEMPSPACE_8K.

Usage Notes: Edits are required to specify valid physical disk locations for your environment (d:\db2\data\data4k), for a database user other than WEBLOGIC and to change buffer pool names.

statistics_build.sql

Builds a file of "runstats" commands for each table that will compute database statistics needed for the database optimizer. Runstats should be run whenever any significant changes in database data occur. Your database administrator will typically schedule "runstats to run periodically in your environment.

install_report.sql

Builds an informational installation report about the database objects created in the WEBLOGIC schema.

bt_create_tablespace.sql

Creates the WEBLOGIC_EVENT_DATA tablespace.

Usage Notes: Edits are required to specify valid physical disk locations for your environment (<event_container>), and to use a buffer pool other than the IBM default buffer pool.

bt_create_users.sql

Creates the WEBLOGIC_EVENT schema owner user, establishes the user's password, default and temporary tablespaces and grants privileges to that user.

Usage Notes: Edits are required to change the schema owner user name, password and tablespace names.

The default schema owner user name and password are the following:

schema owner user: WEBLOGIC

schema owner user password: WEBLOGIC

Script Name	Description
create_user.sql	Grant createtab, bindadd and connect DB2 privileges to the WEBLOGIC schema owner user. Usage Notes: Because IBM DB2 databases authenticate users via the operating system (OS), you need to create an OS user that will own database schema objects. Edits are required to change the schema owner user name. The default schema owner user name and password are the following: schema owner user: WEBLOGIC schema owner user password: WEBLOGIC
create_bufferpool.sql	Create an 8K bufferpool, if one does not already exist. Usage Notes: DB2 must be stopped and restarted to utilize new bufferpools. Edits are required to change the 8K bufferpool name. The default bufferpool is BP8K.
create_tablespaces.sql	Creates a 4K and 8K regular tablespaces. The default tablespace names are the following: WEBLOGIC_DATA_4K: Tables for WebLogic Portal and/or WebLogic Platform with rowsize smaller than 4K. WEBLOGIC_DATA_8K: Tables for WebLogic Portal and/or WebLogic Platform with rowsize larger than 4K and smaller than 8K. Usage Notes: Edits are required to specify valid physical disk locations for your environment (d:\db2\data\data4k), for a database user other than WEBLOGIC and to change buffer pool names.
create_temp_tablespaces.sql	Create an 8K temporary tablespace. The default tablespace name is TEMPSPACE_8K. Usage Notes: Edits are required to specify valid physical disk locations for your environment (d:\db2\data\data4k), for a database user other than WEBLOGIC and to change buffer pool names.
statistics_build.sql	Builds a file of "runstats" commands for each table that will compute database statistics needed for the database optimizer. Runstats should be run whenever any significant changes in database data occur. Your database administrator will typically schedule "runstats to run periodically in your environment.
install_report.sql	Builds an informational installation report about the database objects created in the WEBLOGIC schema.
bt_create_tablespace.sql	Creates the WEBLOGIC_EVENT_DATA tablespace. Usage Notes: Edits are required to specify valid physical disk locations for your environment (<event_container>), and to use a buffer pool other than the IBM default buffer pool.
bt_create_users.sql	Creates the WEBLOGIC_EVENT schema owner user, establishes the user's password, default and temporary tablespaces and grants privileges to that user. Usage Notes: Edits are required to change the schema owner user name, password and tablespace names. The default schema owner user name and password are the following: schema owner user: WEBLOGIC schema owner user password: WEBLOGIC

Start the CLP DB2 tool from the directory that contains the scripts.

From CLP, connect to the database you want to work with. For example, type:

Db2 connect to <DATABASE> user <USER_NAME> password <PASSWORD>

From CLP, run create_bufferpool.sql, if needed. You may not need to create a new 8K bufferpool if you already have one to utilitize. For example, type:

Db2 -tf create_bufferpool.sql -v

Restart your database instance.

From CLP, run create_temp_tablespaces.sql. For example, type:

Db2 -tf create_temp_tablespaces.sql -v

From CLP, run create_tablespaces.sql. For example, type:

Db2 -tf create_tablespaces.sql -v

From CLP, run create_user.sql. For example, type:

Db2 -tf create_user.sql -v

Follow the steps in Manually Creating Database Objects on page 6-5.

Manually Creating Database Objects

You can either manually create database objects or use the Configuration Wizard, see Manually Creating Database Objects and JDBC Settings on page 1-2 for more information.

Note: If you choose to use the WebLogic Configuration Wizard to configure and connect to the database that you will use to support WebLogic Portal, see http://download.oracle.com/docs/cd/E13196_01/platform/docs81/confgwiz/index.html.

To manually create BEA Portal database objects, use the following steps:

From DB2-CLP, use the following command to verify that you can connect to the target database server with a valid user ID and password:

db2 connect to <DATABASE> user <USERNAME> password <PASSWORD>

Open your domain's db_settings.properties file for edit and comment out the database settings for PointBase.

In the db_settings.properties file for your domain, uncomment the database settings for your new target database and update the following settings for your database:

server=
dblogin=
password=

Create the database.

For Windows, navigate to the <BEA_HOME>\user_projects\domains\portalDomain directory, and double-click on the create_db.cmd file.

For UNIX, navigate to the <BEA_HOME>\user_projects\domains\portalDomain directory, run create_db.sh.

Verify the results in the create_db.log file.

Note: If you are using the sample domain, run the create_db.cmd/sh file from the following directory: <BEA_HOME>\weblogic81\samples\domains\portal.

Follow the steps in Manually Configuring Your Domain's JDBC Driver Settings on page 6-6.

Manually Configuring Your Domain's JDBC Driver Settings

You can either manually configure your domains JDBC driver settings using the WebLogic Server Console, or use the Configuration Wizard, see Manually Creating Database Objects and JDBC Settings on page 1-2 for more information.

To manually configure your JDBC Driver settings using WebLogic Server Console,

Start the WebLogic Server for your domain.

Configure your new connection pools.

Go to Services -> JDBC -> Connection Pools.

Click Configure a new Connection Pool.

Select the appropriate Database Type and Non-XA Database Driver from the drop down list boxes and click Continue. For more information, see the Supported Configuration documentation for JDBC drivers supported by WebLogic Portal, http://download.oracle.com/docs/cd/E13196_01/platform/docs81/support/supp_plat.html#1085671.

Note: For an XA configuration, see "Creating XA Domains Using Configuration Templates" in the "Creating WebLogic Configurations Using the Configuration Wizard documentation, http://download.oracle.com/docs/cd/E13196_01/platform/docs81/confgwiz/index.html .

Choose a name for the new Connection Pool (For example: cgPoolN) and fill in the blanks for your vendor database. Click Continue.

Test your connection to verify that you can successfully connect to your database.

Create and deploy your new Connection Pool.

Note: A one-to-one mapping of JDBCTxDataSource to JDBC Connection Pool needs to be maintained in the domain's configuration (as managed in the config.xml file). Create one new JDBC Connection Pool for each JDBCTxDataSource and another JDBC Connection Pool for the domain's JDBCDataSources.

Update your data sources.

From Services -> JDBC -> Data Sources, click on each data source and switch each to the newly created connection pool. Be sure to apply each change.

Verify that each Data Source is changed by clicking on Data Sources and then verifying that Pool Name has been set to the new Connection Pool for each.

From Services -> JMS -> Stores -> cgJMSStore, switch cgJMSStore to use the new Connection Pool.

Stop your domain's WebLogic Server, then restart it.

In the WebLogic Server Console, delete the original connection pools.

Go to Services -> JDBC -> Connection Pools.

Right-click each connection pool and select Delete.

Creating a Database for Behavior Tracking Events

You may want to store behavior tracking events in a different location than other WebLogic Portal database objects for increased performance. For more information about behavior tracking, see http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/adminportal/help/SA_BehavTrackServ.html.

Note: By default, behavior tracking database objects are created in the same database as other WebLogic Portal database objects. You only need to following these steps if you are configuring a separate database for behavior tracking events.

Verify that you can connect to the target database, see step 1. in .

From CLP, run the bt_create_temp_tablespaces.sql script. For example, type,

Db2 -tf bt_reate_temp_tablespaces.sql -v

From CLP, run bt_create_user.sql. For example, type,

Db2 -tf bt_create_user.sql -v

Open your domain's db_settings.properties file for edit.

Within the db_settings.properties file, uncomment the database settings for DB2and update the following settings:

server=<SERVER_NAME>
dblogin=WEBLOGIC_EVENT
password=WEBLOGIC_EVENT

Within the db_settings.properties file, find the p13n_modules, portal_modules and netuix_modules lines at the top of the file.

Copy these 3 lines and comment out the original settings by adding a # sign.

Replace the original settings as follows:

Replace p13n_modules=p13n au bt ds with p13n_modules=bt
Replace portal_modules=cm wlcs wps collaboration sample_cm with portal_modules=
Replace netuix_modules=pf with netuix_modules=

When you are finished, the section should look like this:
#p13n_modules=p13n au bt ds
#portal_modules=cm wlcs wps collaboration sample_cm
#netuix_modules=pf
p13n_modules=bt
portal_modules=
netuix_modules=

Save the changes to the db_settings.properties file.Save the changes to the db_settings.properties file.

Initialize the database schema with the new settings.

For Windows, navigate to the \\bea\user_projects\domains\portalDomain directory, and double-click on the create_db.cmd file.

For UNIX, navigate to the \\bea\user_projects\domains\portalDomain directory, run create_db.sh.

Verify the results in the db.log file.

Note: If you are using the sample domain, run the create_db.cmd/sh file from the following directory: \\bea\weblogic81\samples\domains\portal.

Configure a connection pool to access your behavior tracking database and associate the p13n_tracking JDBC Data Source with that connection pool. Follow the steps in Manually Configuring Your Domain's JDBC Driver Settings on page 6-6.