![]() |
![]() |
|
|
The WebLogic Personalization Server Database Schema
This topic documents the database schema for the WebLogic Personalization Server. This topic includes the following sections:
The Entity-Relation Diagram
Figure 12-1 shows the logical Entity-Relation diagram for the WebLogic Personalization Server database. See the subsequent sections in this topic for information about the data type syntax.
Figure 12-1 Entity-Relation Diagram for the WebLogic Personalization Server
List of Tables Comprising the WebLogic Personalization Server
The WebLogic Personalization Server is comprised of the following tables. In this list, the tables are sorted by functionality:
Ads and Placeholders tables
The PLACEHOLDER_PREVIEW Database Table
Data Synchronization tables
The DATA_SYNC_APPLICATION Database Table
The DATA_SYNC_ITEM Database Table
The DATA_SYNC_SCHEMA_URI Database Table
The DATA_SYNC_VERSION Database Table
Documentation Management tables
The DOCUMENT_METADATA Database Table
Mail tables
The MAIL_ADDRESS Database Table
The MAIL_BATCH_ENTRY Database Table
The MAIL_HEADER Database Table
The MAIL_MESSAGE Database Table
User Management tables
The GROUP_HIERARCHY Database Table
The GROUP_SECURITY Database Table
The USER_GROUP_CACHE Database Table
The USER_GROUP_HIERARCHY Database Table
The USER_PROFILE Database Table
The USER_SECURITY Database Table
Common tables used by both WebLogic Personalization Server and WebLogic Portal
The ENTITLEMENT_RULESET Database Table Database Table
The PROPERTY_KEY Database Table
The PROPERTY_VALUE Database Table
The SAMPLE_UUP_INFO Database Tablee
The WEBLOGIC_IS_ALIVE Database Table
The Personalization Server Data Dictionary
In this section, the WebLogic Personalization Server schema tables are arranged alphabetically as a data dictionary.
Note: Even though the following documentation references "foreign keys" to various tables, these constraints do not currently exist in this release of WebLogic Personalization Server. However, they will be (available in future releases) in place in future versions of WebLogic Personalization Server and we want you to be aware of these relationships now.
The AD_BUCKET Database Table
Table 12-1 describes the AD_BUCKET table. This table maintains content queries for ads.
The Primary Key is AD_BUCKET_ID.
The AD_COUNT Database Table
Table 12-2 describes the AD_COUNT table. This table tracks the number of times the ads are displayed and clicked though.
The Primary Key is comprised of AD_ID, CONTAINER_REF, and APPLICATION_NAME.
The DATA_SYNC_APPLICATION Database Table
Table 12-3 describes the DATA_SYNC_APPLICATION table. This table holds the various applications available for the data synchronization process..
The Primary Key is APPLICATION_ID.
The DATA_SYNC_ITEM Database Table
Table 12-4 describes the DATA_SYNC_ITEM table. This table stores all the data items to be synchronized.
For information on defined constraints in this table, see Defined Constraints.
The Primary Key is DATA_SYNC_ITEM_ID.
The DATA_SYNC_SCHEMA_URI Database Table
Table 12-5 describes the DATA_SYNC_SCHEMA_URI table. This table holds information pertaining to each of the governing schemas used by various documents.
The Primary Key is SCHEMA_URI_ID.
The DATA_SYNC_VERSION Database Table
Table 12-6 describes the DATA_SYNC_VERSION table. This table is not being used currently. It is reserved for future use and is expected to accommodate data synchronization versioning. As a result, this table only holds one record.
The Primary Key is comprised of both VERSION_MAJOR and VERSION_MINOR.
The DOCUMENT Database Table
Table 12-7 describes the DOCUMENT table. This table is used to store information pertinent to each document used within the WebLogic Personalization Server.
The Primary Key is ID.
The DOCUMENT_METADATA Database Table
Table 12-8 describes the DOCUMENT_METADATA table. This table is used to store user-defined properties associated with each document.
For information on defined constraints in this table, see Defined Constraints.
The Primary Key is comprised of both ID and NAME.
The ENTITLEMENT_RULESET Database Table
Table 12-9 describes the ENTITLEMENT_RULESET table. This table stores the access decision rules used by the Entitlements Engine.
The Primary Key is comprised of both APPLICATION_NAME and RULESET_URI.
The ENTITY Database Table
Table 12-10 describes the ENTITY table. Any ConfigurableEntity within the system will have an entry in this table.
The Primary Key is ENTITY_ID.
The GROUP_HIERARCHY Database Table
Table 12-11 describes the PARENT_CHILD_GROUP table. This table stores relationship information between groups.
For information on defined constraints in this table, see Defined Constraints.
The Primary Key is comprised of both PARENT_GROUP_ID and CHILD_GROUP_ID.
The GROUP_SECURITY Database Table
Table 12-12 describes the GROUP_SECURITY table. This table stores relationship information between groups.
The Primary Key is GROUP_ID.
The MAIL_ADDRESS Database Table
Table 12-13 describes the metadata for the E-Business Control Center MAIL_ADDRESS table. This table stores all of the address info for e-mail purposes.
For information on defined constraints in this table, see Defined Constraints.
The Primary Key is MAIL_ADDRESS_ID.
The MAIL_BATCH Database Table
Table 12-14 describes the metadata for the E-Business Control Center MAIL_BATCH table. This table establishes a batch for each mailing.
The Primary Key is BATCH_ID.
The MAIL_BATCH_ENTRY Database Table
Table 12-15 describes the metadata for the E-Business Control Center MAIL_BATCH_ENTRY table. This table is used to correlate the mail batch with the specific mail message.
For information on defined constraints in this table, see Defined Constraints.
The Primary Keys are BATCH_ID and MESSAGE_ID.
The MAIL_HEADER Database Table
Table 12-16 describes the metadata for the E-Business Control Center MAIL_HEADER table. This table contains all of the header information specific to the e-mail message.
For information on defined constraints in this table, see Defined Constraints.
The Primary Key is HEADER_ID.
The MAIL_MESSAGE Database Table
Table 12-17 describes the metadata for the E-Business Control Center MAIL_MESSAGE table. This table contains the specifics of the mail message (e.g., the subject line, text, etc.).
The Primary Key is MESSAGE_ID.
The PLACEHOLDER_PREVIEW Database Table
Table 12-18 describes the PLACEHOLDER_PREVIEW table. This table is used as a mechanism to hold the placeholder for previewing purposes only.
The Primary Key is PREVIEW_ID.
The PROPERTY_KEY Database Table
Table 12-19 describes the PROPERTY_KEY table. Any property assigned to a ConfigurableEntity has a unique PROPERTY_ID. This identifier and associated information is stored here.
The Primary Key is PROPERTY_KEY_ID.
The PROPERTY_VALUE Database Table
Table 12-20 describes the PROPERTY_VALUE table. This table stores property values for boolean, datetime, float, integer, text, and user-defined properties.
For information on defined constraints in this table, see Defined Constraints.
The Primary Key is PROPERTY_VALUE_ID.
The SAMPLE_UUP_INFO Database Table
Table 12-21 describes the SAMPLE_UUP_INFO table. This is an example of how to use the Unified Profile Types.
The Primary Key is USER_NAME.
The SEQUENCER Database Table
Table 12-22 describes the SEQUENCER table. The SEQUENCER table is used to maintain all of the sequence identifiers (for example, property_meta_data_id_sequence, and so on) used in the application.
For information on defined constraints in this table, see Defined Constraints.
The Primary Key is SEQUENCE_NAME.
The USER_GROUP_CACHE Database Table
Table 12-23 describes the USER_GROUP_CACHE table. In the event of a deep group hierarchy, this table will flatten the group hierarchy and enables quick group membership searches.
Note: The startup process GroupCache is disabled by default. This table will only be used if enabled.
The Primary Key is comprised of both USER_NAME and GROUP_NAME.
The USER_GROUP_HIERARCHY Database Table
Table 12-24 describes the USER_GROUP_HIERARCHY table. This table allows you to store associated users and groups.
For information on defined constraints in this table, see Defined Constraints.
The Primary Key is comprised of both GROUP_ID and USER_ID.
The USER_PROFILE Database Table
Table 12-25 describes the USER_PROFILE table. This table stores all user login/password combinations.
The Primary Key is USER_NAME.
The USER_SECURITY Database Table
Table 12-26 describes the USER_SECURITY table. This table holds all the user records for security authentication of the rdbms realm.
The Primary Key is USER_ID.
The WEBLOGIC_IS_ALIVE Database Table
Table 12-27 describes the WEBLOGIC_IS_ALIVE table. This table is used by the JDBC connection pools to insure the connection to the database is still alive.
The Primary Key is NAME.
The SQL Scripts Used to Create the Database
The database schemas for WebLogic Portal and WebLogic Personalization Server are all created by executing the create_all script for the target database environment.
Scripts
Regardless of your database, execute one of the following to generate the necessary database objects for the modules desired (WebLogic Portal, WebLogic Personalization Server, Commerce services, Campaign services and Sample Portal):
The following are the various directories underneath WL_COMMERCE_HOME/db
(as seen in a UNIX environment):
P13N_HOME/db/cloudscape/351
P13N_HOME/db/oracle/817
Note: In this documentation,P13N_HOME is used to designate the directory where the WebLogic Personalization Server product is installed.
Each of the databases supported have the same number of scripts in each of their subdirectories. The scripts are listed and described in Table 12-51 below.
Defined Constraints
Various constraints are defined and used in the WebLogic Personalization Server database schema. These constraints can be found in the following scripts:
p13n_create_fkeys.sql-contains the Foreign Keys
p13n_create_tables.sql-contains the Check Constraints
![]() |
![]() |
![]() |
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|