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

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 needed. Usage Notes: DB2 must be stopped and restarted to utilize new bufferpools. Edits are required to change the 8K bufferpool name. The default tablespace names and bufferpool (TEMPSPACE) 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. TEMPSPACE_8K: Temp space utilized by tables created in the WEBLOGIC_DATA_8K tablespace.
create_temp_tablespaces.sql	Create 4K and 8K regular tablespaces. Usage Notes: Edits are required to specify valid physical disk locations for your environment.
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 modify the pathnames for the DATA_PATHNAME and INDEX_PATHNAME variables to match your local directory path structures. The default tablespace names and bufferpool (TEMPSPACE) 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. TEMPSPACE_8K: Temp space utilized by tables created in the WEBLOGIC_DATA_8K tablespace.
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

From the CLP tool, navigate to the directory that contains the scripts. For example, type:

WL_HOME/portal/db/DB2/8/admin

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_user.sql. For example, type,

Db2 -tf create_user.sql -v

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

Creating Database Objects

To create BEA Platform 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 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 Configuring Your Domain's JDBC Driver Settings on page 5-7.

Configuring Your Domain's JDBC Driver Settings

Note: These settings do not allow support for XA functionality. For instructions on enabling XA, consult XA Support on page 7-1.

Start the WebLogic Server for your domain.
Login to the WebLogic Server Console.
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.
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.
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 cgPool connection pool.
Go to Services -> JDBC -> Connection Pools.
Right-click on the cgPool 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 Manually Configuring Databases.
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 your new target database and update the following settings for your database:
• 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 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. Follow the steps in Configuring Your Domain's JDBC Driver Settings on page 5-7.