Table 6-7 CATALOG_PROPERTY_VALUE Table Metadata Unique identification numbers for configurable entities. The WLCS_PRODUCT_KEYWORD Database Table.The WLCS_PRODUCT_CATEGORY Database Table.The CATALOG_PROPERTY_VALUE Database Table.The CATALOG_PROPERTY_KEY Database Table.The following tables compose the product catalog database. įigure 6-2 and Figure 6-3 show the Entity-Relation for the WebLogic Portal Commerce services core Product Catalog database objects.įigure 6-2 Entity-Relation Diagram for the Core Product Catalog Tablesįigure 6-3 Entity-Relation Diagram for the Core Product Catalog Tables - continued For more information about the Dublin Core Metadata Open Standard, please see. This standard offers a number of advantages for a Web-based catalog. The metadata for items in Commerce services Product Catalog are based on the Dublin Core Metadata Open Standard. The ID of the event that corresponds with the event action taken. This field is one of the table's primary keys. The event action taken such as BEGIN EXPORT or END EXPORT. This table logs actions used by third-party vendors against the recorded event data. The data elements corresponding to each event type are captured in the XML_DEFINITION column of the EVENT table. An XML document is created specifically for each event type. The XML_DEFINITION column contains all information from these five columns plus event data that is unique to each event type. Five of the EVENT table's columns contain data common to every event type. If the user has not logged in this column will be null.Īs shown in Table 6-2, the BT_EVENT table has six columns each column corresponds to a specific event element. The user ID associated with the session and event. It is stored as a CLOB (Character Large Object). A string identifier showing which event was fired.Ī unique, WebLogic Server-generated number assigned to the session.Īn XML document that contains the specific event information for each event type. PK - A unique, system-generated number used as the record ID.įK - Set to BT_EVENT_TYPE. This table references event types and categories in the BT_EVENT table. Figure 6-1 shows an entity-relation diagram for the WebLogic Portal Behavior Tracking Database objects.įigure 6-1 Entity-Relation Diagram for the Behavior Tracking Database The BT_EVENT_ACTION table logs actions used by third-party vendors against the recorded event data, and the BT_EVENT_TYPE table references event types and categories in the EVENT table. The BT_EVENT table stores all event data. Three tables are provided for the Behavior Tracking data. This section describes the requirements and database objects needed to log event data for analytical use. You can use the knowledge gained from analysis to create and optimize personalization rules, set up product offers, and develop interactive marketing campaigns. Analytics Marketing systems can then analyze these events offline to evaluate visitor behavior and transactional data. These kinds of events are called Behavior Tracking events. To record how online visitors are interacting with your Web site, you can record event information to a database. Note: WebLogic Portal DDL Modules identifies the filenames and location of DDL (database definition language) files for each set of Portal Database objects. Tracked Anonymous User Database Objects.WebLogic Portal Services Database Objects.This section includes information on the following subjects: Whether or not null values are allowed to be stored for the column.Ī detailed description of the contents and purpose for the column including Primary Key (PK-) and Foreign Key (FK-) designations. For instance, Columns defined as BLOB data types in Oracle, DB2, and PointBase would be defined as TEXT columns in Microsoft SQL Server and Sybase. The predefined characteristics for the column.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |