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. These scripts are available in: <WL_HOME>\portal\db\sql_server\2000\admin. The sample scripts use the following defaults:

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

Script Name	Description
create_database.sql	Create the WEBLOGIC database and WEBLOGIC database owner user login. An alias is created to make WEBLOGIC dbo in the database. Make the WebLogic database the default database for the WebLogic user. Usage Notes: You need to change database names, database owner user and password. The default names are the following: database name: WEBLOGIC database owner user: WEBLOGIC password: WEBLOGIC You also need to edit the script to reflect valid disk locations for DATA and the LOG devices, or to adjust file sizes. DATA and LOG files should be placed on separate physical disks and away from any system database files.
statistics.sql	Runs sp_updatestats to compute database statistics needed for the database optimizer. Analyze schema should be run whenever any significant changes in database data occur. Your database administrator will typically schedule sp_updatestats to run periodically in your environment.
install_report.sq	Builds an informational installation report about the database objects created in the WEBLOGIC schema.
bt_create_database.sql	Create the WEBLOGIC_EVENT database and WEBLOGIC_EVENT database owner user login. An alias is created to make WEBLOGIC_EVENT dbo in the database. Usage Notes: You need to change database names, database owner user and password. The default names are the following: database name: WEBLOGIC_EVENT database owner user: WEBLOGIC_EVENT password: WEBLOGIC_EVENT You also need to edit the script to reflect valid disk locations for DATA and the LOG devices, or to adjust file sizes. DATA and LOG files should be placed on separate physical disks and away from any system database files.

Run create_database.sql via OSQL as a user with System Administrator privileges (i.e. the sa user). For example:

osql -Usa -SSQLSERVER -e -icreate_database.sql -ocreate_database.log

The output from running create_database.sql is written to create_database.log. Verify that there are no errors in the log file before proceeding.

Creating Database Objects

The scripts to create Microsoft SQL Server database objects were designed to run in a Windows environment (they use the OSQL utility to create Microsoft SQL Server database objects). If you are using UNIX version of WebLogic Server with a Microsoft SQL Server database and do not have WebLogic products also installed on Windows contact BEA support for assistance.

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

Verify that you can connect to the target database server with a valid user ID and password. For example:

osql -SSQLSERVER -U<userid> -P<password>

Open your domain's 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.
Verify the results in the db.log file.

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

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

Configuring 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 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 follow 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.
Run bt_create_database.sql via OSQL as a user with system administrator privileges (i.e. the sa user). For example:

osql -Usa -SSQLSERVER -e -ibt_create_database.sql -obt_create_database.log

The output from running bt_create_database.sql is written to bt_create_database.log. Verify that there are no errors in the log file before proceeding.

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.
Navigate to the <BEA_HOME>\user_projects\domains\portalDomain directory, and double-click on the create_db.cmd file.
Verify the results in the db.log file.

Note: If you are using the sample domain, run the create_db.cmd file from the following directory: <BEA_HOME>\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 2-6.