Campaign Manager Database Schema

 

This topic describes the database schema for the Campaign services. Understanding this schema will be helpful to those who may be customizing or extending the technologies provided in the product.

This topic includes the following sections:

• The Entity-Relation Diagram

• List of Tables Composing the BEA Campaign Manager

• The Campaign Manager Data Dictionary

• The SQL Scripts Used to Create the Database

• Defined Constraints

 

---

The Entity-Relation Diagram

Figure 5-1 shows the Entity-Relation diagram for the E-Business Control Center for the Campaign services database. See the subsequent sections in this chapter for information about the data type syntax.

Figure 5-1 Entity-Relation Diagram for Campaign Manager Database Tables

 

 

---

List of Tables Composing the BEA Campaign Manager

The BEA Campaign Manager is composed of the following table:

Campaign and Scenarios

• The SCENARIO_END_STATE Database Table

 

---

The Campaign Manager Data Dictionary

At this time, there is only one database table pertaining to the Campaign Manager.

See also the chapter "The WebLogic Personalization Server Database Schema" in the Guide to Building Personalized Applications.

The SCENARIO_END_STATE Database Table

Table 5-1 describes the metadata for the E-Business Control Center SCENARIO_END_STATE table. This table identifies when a user is no longer eligible to participate in a particular scenario.

The Primary Keys are SCENARIO_XML_REF, USER_NAME, CONTAINER_REF, CONTAINER_TYPE and APPLICATION_NAME.

Table 5-1 SCENARIO_END_STATE Table Metadata

Column Name	Data Type	Null Value	Description and Recommendations
SCENARIO_XML_REF	VARCHAR(20)	NOT NULL	PK—The identifier for the XML-based scenario definition file.
USER_NAME	VARCHAR(200)	NOT NULL	PK—the user ID. (FK to WLCS_USER.IDENTIFIER)
CONTAINER_REF	VARCHAR(254)	NOT NULL	PK—the campaign unique identifier. (FK to CAMPAIGN.CAMPAIGN_UID)
CONTAINER_TYPE	VARCHAR(50)	NOT NULL	PK—At this time this column will always hold the string 'Campaign'.
APPLICATION_NAME	VARCHAR(100)	NOT NULL	PK—The deployed J2EE application name. This should match the name in the WebLogic Server console.)

 

 

---

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):

• PORTAL_HOME\db\create_all.bat (Windows)

• PORTAL_HOME/db/create_all.sh (UNIX)

  The following are the various directories underneath WL_COMMERCE_HOME/db
  (as seen in a UNIX environment):

  PORTAL_HOME/db/cloudscape/351

  PORTAL_HOME/db/oracle/817

Note: In this documentation,PORTAL_HOME is used to designate the directory where the 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 5-2 below.

Table 5-2 The Scripts Supporting the Databases

Script Name	Description
create_all.bat	Windows script used to connect to the database and create the necessary database objects for the modules desired (e.g., WebLogic Portal, WebLogic Personalization Server, Commerce services, Campaign services and Sample Portal)
create_all.sh	Unix script used to connect to the database and create the necessary database objects for the modules desired (e.g., WebLogic Portal, WebLogic Personalization Server, Commerce services, Campaign services and Sample Portal)
campaign_create_fkeys.sql	SQL script used to create all foreign keys associated with the Campaign services.
campaign_create_indexes.sql	SQL script used to create all indexes associated with the Campaign services.
campaign_create_tables.sql	SQL script used to create all tables associated with the Campaign services.
campaign_create_triggers.sql	SQL script used to create all database triggers associated with the Campaign services.
campaign_create_views.sql	SQL script used to create all views associated with the Campaign services.
campaign_drop_constraints.sql	SQL script used to drop all constraints (other than foreign keys) associated with the Campaign services.
campaign_drop_fkeys.sql	SQL script used to drop all foreign key constraints associated with the Campaign services.
campaign_drop_indexes.sql	SQL script used to drop all indexes associated with the Campaign services.
campaign_drop_tables.sql	SQL script used to drop all tables associated with the Campaign services.
campaign_drop_views.sql	SQL script used to drop all views associated with the Campaign services.
p13n_create_fkeys.sql	SQL script used to create all foreign keys associated with the WebLogic Personalization Server.
p13n_create_indexes.sql	SQL script used to create all indexes associated with the WebLogic Personalization Server.
p13n_create_tables.sql	SQL script used to create all tables associated with the WebLogic Personalization Server.
p13n_create_triggers.sql	SQL script used to create all database triggers associated with the WebLogic Personalization Server.
p13n_create_views.sql	SQL script used to create all views associated with the WebLogic Personalization Server.
p13n_drop_constraints.sql	SQL script used to drop all constraints (other than foreign keys) associated with the WebLogic Personalization Server.
p13n_drop_fkeys.sql	SQL script used to drop all foreign key constraints associated with the WebLogic Personalization Server.
p13n_drop_indexes.sql	SQL script used to drop all indexes associated with the WebLogic Personalization Server.
p13n_drop_tables.sql	SQL script used to drop all tables associated with the WebLogic Personalization Server.
p13n_drop_views.sql	SQL script used to drop all views associated with the WebLogic Personalization Server.
portal_create_fkeys.sql	SQL script used to create all foreign keys associated with the WebLogic Portal.
portal_create_indexes.sql	SQL script used to create all indexes associated with the WebLogic Portal.
portal_create_tables.sql	SQL script used to create all tables associated with the WebLogic Portal.
portal_create_triggers.sql	SQL script used to create all database triggers associated with the WebLogic Portal.
portal_create_views.sql	SQL script used to create all views associated with the WebLogic Portal.
portal_drop_constraints.sql	SQL script used to drop all constraints (other than foreign keys) associated with the WebLogic Portal.
portal_drop_fkeys.sql	SQL script used to drop all foreign key constraints associated with the WebLogic Portal.
portal_drop_indexes.sql	SQL script used to drop all indexes associated with the WebLogic Portal.
portal_drop_tables.sql	SQL script used to drop all tables associated with the WebLogic Portal.
portal_drop_views.sql	SQL script used to drop all views associated with the WebLogic Portal.
sample_portal_create_fkeys.sql	SQL script used to create all foreign keys associated with the Sample Portal.
sample_portal_create_indexes.sql	SQL script used to create all indexes associated with the Sample Portal.
sample_portal_create_tables.sql	SQL script used to create all tables associated with the Sample Portal.
sample_portal_create_triggers.sql	SQL script used to create all database triggers associated with the Sample Portal.
sample_portal_create_views.sql	SQL script used to create all views associated with the Sample Portal.
sample_portal_drop_constraints.sql	SQL script used to drop all constraints (other than foreign keys) associated with the Sample Portal.
sample_portal_drop_fkeys.sql	SQL script used to drop all foreign key constraints associated with the Sample Portal.
sample_portal_drop_indexes.sql	SQL script used to drop all indexes associated with the Sample Portal.
sample_portal_drop_tables.sql	SQL script used to drop all tables associated with the Sample Portal.
sample_portal_drop_views.sql	SQL script used to drop all views associated with the Sample Portal.
wlcs_create_fkeys.sql	SQL script used to create all foreign keys associated with the Commerce services.
wlcs_create_indexes.sql	SQL script used to create all indexes associated with the Commerce services.
wlcs_create_tables.sql	SQL script used to create all tables associated with the Commerce services.
wlcs_create_triggers.sql	SQL script used to create all database triggers associated with the Commerce services.
wlcs_create_views.sql	SQL script used to create all views associated with the Commerce services.
wlcs_drop_constraints.sql	SQL script used to drop all constraints (other than foreign keys) associated with the Commerce services.
wlcs_drop_fkeys.sql	SQL script used to drop all foreign key constraints associated with the Commerce services.
wlcs_drop_indexes.sql	SQL script used to drop all indexes associated with the Commerce services.
wlcs_drop_tables.sql	SQL script used to drop all tables associated with the Commerce services.
wlcs_drop_views.sql	SQL script used to drop all views associated with the Commerce services.

 

 

---

Defined Constraints

There are not constraints associated with this part of the schema.

.