![]() ![]() ![]() ![]() ![]() ![]() ![]() |
This chapter describes the steps necessary to use a Sybase database with WebLogic Portal, and includes the following sections:
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 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). GroupSpace requires a separate database, as do any additional content management repositories.
Notes: | 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. |
Note: | 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:
WL_HOME
\portal\db\sybase\admin
directory. See
Table 7-1, Database Scripts and Usage Notes, on page 7-7 and the comments in the scripts for additional information.
To configure the main WebLogic Portal database, follow these steps:
create_devices.sql
script and modify it appropriately for your environment. See
Table 7-1, Database Scripts and Usage Notes, on page 7-7 and the comments in the script for additional information. 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
create_database.sql
script and modify it appropriately for your environment. See
Table 7-1, Database Scripts and Usage Notes, on page 7-7 and the comments in the script for additional information. create_database.sql
as a user with system administrator privileges (normally the sa
user). For example, using isql
:isql -Usa -S
MYSYBASE
-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 Creating WebLogic Configurations Using the Configuration Wizard.
database.properties
file for edit.database=sybase
. sybase.user=@DB_USER@
sybase.password=@DB_PASSWORD@
sybase.url=jdbc:bea:sybase://@DB_HOST@:@DB_PORT@;DatabaseName=@DB_NAME@
appsGroupSpaceDataSource
), which point to PointBase 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 BEA supports are available in the WL_HOME
\portal\db\jdbc\
database_driver directory; for example, sybase_bea
. Follow the instructions in the WL_HOME
\portal\db\jdbc\README.txt
file.
To configure the GroupSpace database, follow these steps:
create_devices.sql
script and modify it appropriately for your environment. See
Table 7-1, Database Scripts and Usage Notes, on page 7-7 and the comments in the script for additional information. 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
create_database.sql
script and modify it appropriately for your environment. See
Table 7-1, Database Scripts and Usage Notes, on page 7-7 and the comments in the script for additional information. create_database.sql
as a user with system administrator privileges (normally the sa
user). For example, using isql
:isql -Usa -S
MYSYBASE
-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 Creating WebLogic Configurations Using the Configuration Wizard.
groupspace_database.properties
file for edit.database=sybase
. sybase.user=@DB_USER@
sybase.password=@DB_PASSWORD@
sybase.url=jdbc:bea:sybase://@DB_HOST@:@DB_PORT@;DatabaseName=@DB_NAME@
appsGroupSpaceDataSource
JDBC data source (which points to PointBase by default) with a data source that points to Sybase. Use the WebLogic Server Administration Console or update the sample jdbc.xml
definition file provided for each database and driver that BEA supports, in the WL_HOME
\portal\db\jdbc\
database_driver directory; for example sybase_bea
. Follow the instructions in the WL_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 Interaction Management Guide.
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:
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 7-1, Database Scripts and Usage Notes, on page 7-7.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
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
WL_HOME
\portal\db\sybase.
WEBLOGIC_EVENT
and run the following scripts:WL_HOME
\portal\db\data\required
:p13n.trackingDataSource
with that data source and then remove p13n.trackingDataSource
from p13nDataSource
.
Table 7-1 describes the scripts that enable you to configure the Sybase database.
Creates database devices. Database devices must be created by a user with system administrator privileges (normally the
sa user).
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.
|
|||||
Creates the database and login. You must create a main WebLogic Portal database. If you want to use GroupSpace, you must create that database. You must also create a database for each additional content management repository. The devices created by
create_devices.sql are used and indexes are placed in their own WEBLOGIC_INDEX segment. An alias is added to the database owner (dbo) user of the database.
Make a copy of this script and edit it to replace
<<WEBLOGIC>> with the appropriate database name, database user, and password for each database you create. Also adjust database and log sizes as appropriate.
If the database you are creating is a development database (and therefore database recovery is not a concern), you can uncomment and set the
truncate log on checkpoint option to true .
If your applications will use WebLogic Workshop for create database or RowSet controls, uncomment and set the
DDL in transaction option to true ; otherwise create commands will not work properly.
When you run the script with these values, it creates the
WEBLOGIC database, the WEBLOGIC_INDEX file group, and WEBLOGIC database owner (dbo) user login. An alias is created to make WEBLOGIC the dbo user in the database. It also sets the WEBLOGIC database as the default database for the WEBLOGIC user.
|
|||||
Creates behavior tracking database devices. Database devices must be created by a user with system administrator privileges (normally the
sa user).
You must also edit the script to reflect valid disk locations for
D:\DATAFILE , E:\LOGFILE , and F:\INDEXFILE device locations; you may also need to modify file sizes. 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.
|
|||||
Create the
WEBLOGIC_EVENT database and WEBLOGIC_EVENT database owner user login. An alias is created to make WEBLOGIC_EVENT the database owner (dbo) user in the database.
|
![]() ![]() ![]() |