Database Administration Guide

Using an Oracle Database

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

Review this entire chapter and any release notes before proceeding. Typically, the steps described in this chapter should be performed by an Oracle system administrator or a database administrator.

Configuring an Oracle Database

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

Note the following when defining your Oracle instance and databases.

Be sure that you are using a supported version, see http://download.oracle.com/docs/cd/E13196_01/platform/docs81/support/supp_plat.html#1085671.
Define a blocksize of at least 8K for increased performance.

Install the Oracle client software on the WebLogic Platform host.

Configure a Local Net Service to access the target Oracle instance.

Be sure that Oracle environment variables are defined, and that the Oracle bin directory is included in the $PATH variable.

Verify that you can connect to the target Oracle database schema via SQLPlus.

Note: If you plan to use the Configuration Wizard to create the database objects for a new domain, you do not need to install the Oracle Client.

Prepare the Oracle database and schema. 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.

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

Be sure to back up your database(s) and schema(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 Manually Creating Database Objects on page 4-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 WebLogic Portal 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 Oracle 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 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 Configure Your Domain's JDBC Driver Settings on page 4-6.

Manually Configure 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.

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 instance, see step 1. in .

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 Oracle and 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.

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