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

Edit the SAMPLE scripts provided in: <WL_HOME>/portal/db/oracle/817/admin to suit your environment.

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 schema owner users and tablespaces needed for your environment.

Review the Description and Usage Notes for each script.

Script Name	Description
create_tablespaces.sql	Creates data and index tablespaces. Usage Notes: Edits are required to modify the pathnames for the DATA_PATHNAME and INDEX_PATHNAME variables to match your local directory path structures. For example, on a UNIX system, if two disks are mounted as /usr1 and /usr2 and the Oracle SID is PROD, use the following pathnames: DEFINE DATA_PATHNAME=/usr1/oradata/PROD DEFINE INDEX_PATHNAME=/usr2/oradata/PROD Edits are also required if you want to change the tablespace names. The following defaults are used: WEBLOGIC_DATA: tables for WebLogic Portal and/or WebLogic Platform WEBLOGIC_INDEX: indexes for WebLogic Portal and/or WebLogic Platform
create_users.sql	Creates a WEBLOGIC schema owner user, establishes the users 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 following defaults are used: database user = WEBLOGIC database password = WEBLOIGIC default tablespace = WEBLOGIC_DATA temporary tablespace = TEMP
rebuild_indexes.sql	Rebuilds WEBLOGIC (schema user) indexes to move them from the WEBLOGIC_DATA tablespace to the WEBLOGIC_INDEX tablespace.
statistics.sql	Runs analyze_schema to compute database statistics needed for the Oracle optimizer. Analyze schema should be run whenever any significant changes in database data occur. Your database administrator will typically schedule analyze_schema to run periodically in your environment.
install_report.sql	Builds an informational installation report about the database objects created in the schema.
db_size.sql	Builds a report showing free space in database tablespaces.
bt_create_tablespaces.sql	Creates the tablespace for behavior event tracking. Usage Notes: Edits are required to modify the pathnames for the EVT_DATA_PATHNAME and INDEX_PATHNAME variables to match your local directory path structures. WEBLOGIC_DATA: tables for WebLogic Portal and/or WebLogic Platform WEBLOGIC_INDEX: indexes for WebLogic Portal and/or WebLogic Platform
bt_create_users.sql	Creates a behavior event tracking 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. Edits are required to change file sizes and device names. The following defaults are used: database user: WEBLOGIC_EVENT password: WEBLOGIC_EVENT

To run these scripts from a shell, change directories to:

WL_HOME/portal/db/oracle/817/admin

Start SQL*Plus as the system user. For example:

sqlplus system/manager@MYDB

From SQL*Plus, execute the create_tablespaces.sql script. using the @ sign. For example:

@create_tablespaces.sql

From SQL*Plus, execute the create_users.sql script using the @ sign. For example,

@create_users.sql

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

Creating Database Objects

To create WebLogic Platform database objects, use the following steps:

Use the following command to verify that you can connect to the target database server with a valid user ID and password:

sqlplus user_ID/password@DB_SID

Open your domains db_settings.properties file for edit and comment out the database settings for PointBase.
Uncomment the database settings for your new target database and update the following settings for your database:
• server=
• dblogin=
• password=
Initialize the database with the new settings.
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 Configure Your Domain's JDBC Driver Settings on page 3-6.

Configure Your Domain's JDBC Driver Settings

Note: These settings do not allow support for XA functionality. For instructions on enabling XA, consult About XA.

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 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.
Move indexes to the WEBLOGIC_INDEX tablespace by executing rebuild_indexes.sql from SQLPLUS. This should be done while WebLogic Server is not running, and is recommended for performance.

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 SQL*Plus, execute the bt_create_tablespaces.sql script. using the @ sign. For example:

@bt_create_tablespaces.sql

From SQL*Plus, execute the bt_create_users.sql script using the @ sign. For example,

@bt_create_users.sql

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.
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 Configure Your Domain's JDBC Driver Settings on page 3-6.