Oracle® Fusion Middleware Database Administration Guide for Oracle WebLogic Portal 10g Release 3 (10.3.4) Part Number E14233-02 |
|
|
View PDF |
This chapter describes the steps necessary to use a Sybase database with WebLogic Portal, and includes the following sections:
Section 8.2, "Configuring the Main WebLogic Portal Database"
Section 8.3, "Manually Creating a Separate Database and Database Objects for Behavior Tracking"
Review this entire chapter and any release notes before proceeding. The tasks in this chapter should be performed by a database administrator.
Before proceeding, read Section 2.1, "Overview of Enterprise-Quality Database Configuration for WebLogic Portal."
The database creation scripts install domain-specific tables. It is recommended that you work with your database administrator to modify the sample scripts, and to create the database users and devices needed for your Sybase environment.
Multiple databases are required if you have multiple domains, or to run multiple environments using the same Sybase instance (for example, if you want to run your test environment and enterprise-quality system from a single Sybase installation). Any additional content management repositories require a separate user.
Note:
You must define a page size of at least 8K to support WebLogic Portal's use of wide tables, wide columns, and larger indexes. For Sybase the default page size is 2K, and Sybase does not allow rows to span pages. If your Sybase instance uses 2k or 4k pages, create a new Sybase instance with an 8K page size. Sybase provides a migration utility to migrate data between servers of different page sizes.If a Sybase instance is defined with a page size smaller than 8K, the WebLogic Portal tables are created but warning messages may be issued at creation time, indicating that the row size could exceed the row size limit. These warnings may result in runtime exceptions, depending on the data being inserted or updated. Indexes will fail to create if they are larger than the maximum page size for the Sybase instance. This could result in data issues as well as performance problems.
To configure a Sybase database:
Be sure to back up your database before installing any new database objects. See your database vendor documentation for details.
Review the provided sample scripts, located in the <WLPORTAL_HOME>\portal\db\sybase\admin
directory. See Table 8-1 and the comments in the scripts for additional information.
Copy and modify the sample scripts appropriately for your environment to create each of the following databases:
Follow the steps in Section 8.2, "Configuring the Main WebLogic Portal Database" to create the main WebLogic Portal database and database objects.
If you want to create a separate behavior tracking database, follow the steps in Section 8.3, "Manually Creating a Separate Database and Database Objects for Behavior Tracking."
To configure the main WebLogic Portal database, follow these steps:
Copy the create_devices.sql
script and modify it appropriately for your environment. See Table 8-1 and the comments in the script for additional information.
Run the modified create_devices.sql
as a user with system administrator privileges (normally the sa
user). For example, using isql
:
isql -Usa -SMYSYBASE -e -icreate_devices.sql -ocreate_devices.log
Copy the create_database.sql
script and modify it appropriately for your environment. See Table 8-1 and the comments in the script for additional information.
Run the modified create_database.sql
as a user with system administrator privileges (normally the sa
user). For example, using isql
:
isql -Usa -SMYSYBASE -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.
Follow the remaining steps only if you want to create database objects manually rather than using the Configuration Wizard. To perform the remaining steps using the Configuration Wizard, see Oracle Fusion Middleware Creating Domains Using the Configuration Wizard.
Open your domain's database.properties
file for edit.
Set database=sybase
.
Update the following settings (by replacing the @ symbols and the text between the symbols with the correct values) for your main WebLogic Portal database:
sybase.user=@DB_USER@ sybase.password=@DB_PASSWORD@ sybase.url=jdbc:bea:sybase://@DB_HOST@:@DB_PORT@;DatabaseName=@DB_NAME@
Create the database objects. You can use the Configuration Wizard or follow these steps:
Navigate to the <MW_HOME>\user_projects\domains\
myPortalDomain
directory.
Enter one of the commands:
On Windows, double-click create_db.cmd
.
On UNIX, run create_db.sh
.
If any error messages are displayed, check the create_db.log
file for additional information.
Note:
After running create_db script, you need to update the database administrator password. See Section 3.8, "Note About Creating or Refreshing Database Objects" for detailed information.Replace the JDBC data sources in your domain, which point to Derby by default, with data sources that point to SQL Server. You can configure them using the WebLogic Server Administration Console or choose from the samples provided and update them for your database environment. Sample jdbc.xml
definition files for each database and driver that Oracle supports are available in the <WLPORTAL_HOME>\portal\db\jdbc\
database_driver
directory; for example, sybase_bea
. Follow the instructions in the <WLPORTAL_HOME>\portal\db\jdbc\README.txt
file.
For improved performance, you might want to store behavior tracking events in a different location from other WebLogic Portal database objects. For more information about behavior tracking, see "Setting Up Events and Behavior Tracking" in the Oracle Fusion Middleware Interaction Management Guide for Oracle WebLogic Portal.
Note:
By default, behavior tracking database objects are created in the same database as other WebLogic Portal database objects. You need to perform these steps only if you are configuring a separate database for behavior tracking events.To create a separate database for behavior tracking:
Edit the bt_create_devices.sql
file and the bt_create_database.sql
file for your environment, as indicated in the instructions contained in the scripts and in Table 8-1.
Run bt_create_devices.sql
as a user with system administrator privileges. For example, using isql
:
isql -Usa -SMYSYBASE -e -ibt_create_devices.sql -obt_create_devices.log
Run bt_create_database.sql
as a user with system administrator privileges. For example, using isql
:
isql -Usa -SMYSYBASE -e -ibt_create_database.sql -obt_create_database.log
Navigate to the appropriate database directory based on your environment; for example, <WLPORTAL_HOME>\portal\db\sybase.
Connect as the user WEBLOGIC_EVENT
and run the following scripts:
bt_create_tables.sql
bt_create_fkeys.sql
bt_create_indexes.sql
bt_create_triggers.sql
Run the following scripts from the path <WLPORTAL_HOME>\portal\db\data\required
:
bt_insert_system_data.sql
bt9_insert_system_data.sql
Use the WebLogic Server Administration Console to configure a non-XA JDBC data source to access your behavior tracking database. Associate the JNDI name p13n.trackingDataSource
with that data source and then remove p13n.trackingDataSource
from p13nDataSource
.
Table 8-1 describes the scripts that enable you to configure the Sybase database.
Table 8-1 Database Scripts and Usage Notes
Script Name | Description |
---|---|
create_devices.sql |
Creates database devices. Database devices must be created by a user with system administrator privileges (normally the
Optimally, locate data, log, and index devices on separate physical disks (with separate controllers) and away from any system database files, unless you are using RAID devices. Note: Do not change the name of the Typical device names for the main WebLogic Portal database are:
|
create_database.sql |
Creates the database and login. You must create a main WebLogic Portal database. You must also create a database for each additional content management repository. The devices created by Make a copy of this script and edit it to replace If the database you are creating is a development database (and therefore database recovery is not a concern), you can uncomment and set the If your applications will use Oracle Enterprise Pack for Eclipse (OEPE) for create database or RowSet controls, uncomment and set the Typical names for the main WebLogic Portal database are:
Note: Do not change the name of the When you run the script with these values, it creates the Note: If you decide to create an additional content management repository, you must create a database with different user names for it. See the Oracle Fusion Middleware Content Management Guide for Oracle WebLogic Portal. |
statistics_build.sql |
Builds |
install_report_build.sql install_report_static.sql |
Builds an informational installation report about the database objects created by the |
bt_create_devices.sql |
Creates behavior tracking database devices. Database devices must be created by a user with system administrator privileges (normally the You must also edit the script to reflect valid disk locations for The following default names are used:
|