![]() |
![]() |
|
|
The Product Catalog Database Schema
This topic documents the database schema for the WebLogic Commerce Server Product Catalog. This topic includes the following sections:
The Entity-Relation Diagram
Figure 2-1 shows the logical Entity-Relation diagram for the WebLogic Commerce Server core product catalog tables in the Commerce database. See the subsequent sections in this chapter for information about the data type syntax.
Figure 2-1 Entity-Relation Diagram for the Core Product Catalog Tables
Figure 2-2 shows the database tables that are used to store different types of custom attributes for product items. These custom attributes are optionally defined by a Web site administrator and are implemented as Property Sets. For more on defining custom attributes, see the section Defining Custom Attributes for Items. Figure 2-2 Custom Attribute Tables for Catalog
The Catalog Schema Is Based on Dublin Core Standard
The metadata for items in WebLogic Commerce Server product catalog are based on the Dublin Core Metadata Open Standard. This standard offers a number of advantages for a Web-based catalog:
The Dublin Core is intended to be usable by non-catalogers as well as resource description specialists. Most of the elements have commonly understood semantics that is roughly the complexity of a library catalog card.
In an Internet environment, disparate description models interfere with the ability to search across discipline boundaries. Promoting a commonly understood set of descriptors that helps to unify other data content standards increases the possibility of semantic interoperability across disciplines.
Recognition of the international scope of resource discovery on the Web is critical to the development of effective discovery infrastructure. The Dublin Core benefits from active participation and promotion in some 20 countries in North America, Europe, Australia, and Asia.
The Dublin Core provides an economical alternative to more elaborate description models such as the full MARC cataloging of the library world. Additionally, Dublin Core includes sufficient flexibility and extensibility to encode the structure and more elaborate semantics inherent in richer description standards
The diversity of metadata needs on the Web requires an infrastructure that supports the coexistence of complementary, independently maintained metadata packages. The World Wide Web Consortium (W3C) has begun implementing an architecture for metadata for the Web. The Resource Description Framework, or RDF, is designed to support the many different metadata needs of vendors and information providers. Representatives of the Dublin Core effort are actively involved in the development of this architecture, bringing the digital library perspective to bear on this important component of the Web infrastructure.
For more information about the Dublin Core Metadata Open Standard, please see http://purl.org/dc.
The Catalog Schema Metadata Tables
This section covers the following database tables:
The WLCS_CATEGORY Database Table
The WLCS_PRODUCT Database Table
The WLCS_PRODUCT_CATEGORY Database Table
The WLCS_PRODUCT_KEYWORD Database Table
The WLCS_SCHEMA Database Table
The WLCS_CATEGORY Database Table
Table 8-1 describes the metadata for the WebLogic Commerce Server WLCS_CATEGORY table. This table is used to store categories in the Commerce database. The descriptions shown in the table reflect the "recommended best practice" for the use of that field by the Dublin Core standard.
The Primary Key is CATEGORY_ID.
See the section The SQL Scripts Used to Create the Database for information about the constraint defined for this table.
The WLCS_PRODUCT Database Table
Table 8-2 describes the metadata for the WebLogic Commerce Server WLCS_PRODUCT table. This table is used to store item records in the Commerce database. The descriptions shown in the table reflect the "recommended best practice" for the use of that field by the Dublin Core standard.
The Primary Key is SKU.
See the section The SQL Scripts Used to Create the Database for information about the constraint defined for this table.
The WLCS_PRODUCT_CATEGORY Database Table
Table 8-3 describes the metadata for the WebLogic Commerce Server WLCS_PRODUCT_CATEGORY table in the Commerce database. This table is used to join categories and items.
The Primary Keys are SKU and CATEGORY_ID.
See the section The SQL Scripts Used to Create the Database for information about the constraint defined for this table.
The WLCS_PRODUCT_KEYWORD Database Table
Table 8-4 describes the metadata for the WebLogic Commerce Server WLCS_PRODUCT_KEYWORD table in the Commerce database. This table stores the keywords that you associate with each product item. The keywords enable rapid retrieval of item records via the search functions on the Web site's pages or Administration pages.
The Primary Keys are KEYWORD and SKU.
See the section The SQL Scripts Used to Create the Database for information about the two constraints defined for this table.
The WLCS_SCHEMA Database Table
Table 2-5 describes the WLCS_SCHEMA table. This table stores property set definitions.
The Primary Keys are SCHEMA_GROUP_NAME and SCOPE_NAME.
The WLCS_CAT_PROP_* Database Tables for Custom Attributes
This section describes several database tables that are used to store different types of custom attributes for product items. These custom attributes are optionally defined by a Web site administrator and are implemented as Property Sets. For more information about defining custom attributes, see the section Defining Custom Attributes for Items.
In this section, the database tables for custom attributes are listed alphabetically, as a data dictionary.
The WLCS_CAT_ENTITY_ID Database Table
Table 8-5 describes the metadata for the WebLogic Commerce Server WLCS_CAT_ENTITY_ID table in the Commerce database. This table stores unique identification numbers for configurable entities.
The Primary Keys are JNDI_HOME_NAME and PK_STRING.
The WLCS_CAT_PROP_BOOLEAN Database Table
Table 8-6 describes the metadata for the WebLogic Commerce Server WLCS_CAT_PROP_BOOLEAN table in the Commerce database. This table stores Boolean property values that are associated with configurable entities.
The WLCS_CAT_PROP_DATETIME Database Table
Table 8-7 describes the metadata for the WebLogic Commerce Server WLCS_CAT_PROP_DATETIME table in the Commerce database. This table stores timestamp property values that are associated with configurable entities.
The WLCS_CAT_PROP_FLOAT Database Table
Table 8-8 describes the metadata for the WebLogic Commerce Server WLCS_CAT_PROP_FLOAT table in the Commerce database. This table stores integer property values that are associated with configurable entities.
The WLCS_CAT_PROP_ID Database Table
Table 8-9 describes the metadata for the WebLogic Commerce Server WLCS_CAT_PROP_ID table in the Commerce database. This table stores unique identification numbers for scoped property names that are associated with configurable entities.
The WLCS_CAT_PROP_INTEGER Database Table
Table 8-10 describes the metadata for the WebLogic Commerce Server WLCS_CAT_PROP_INTEGER table in the Commerce database. This table stores integer property values that are associated with configurable entities.
The WLCS_CAT_PROP_TEXT Database Table
Table 8-11 describes the metadata for the WebLogic Commerce Server WLCS_CAT_PROP_TEXT table in the Commerce database. This table stores text property values that are associated with configurable entities.
The WLCS_CAT_PROP_USER_DEFINED Database Table
Table 2-13 describes the metadata for the WebLogic Commerce Server WLCS_CAT_PROP_USER_DEFINED table in the Commerce database. This table stores user-defined (object) property values that are associated with configurable entities.
The WLCS_PROP_MD_* Database Tables
The WLCS_PROP_MD Database Table
Table 2-14 describes the WLCS_PROP_MD table. This table stores information about defined properties in a property set.
The Primary Keys are SCHEMA_ID and PROPERTY_NAME.
The WLCS_PROP_MD_BOOLEAN Database Table
Table 2-15 describes the WLCS_PROP_MD_BOOLEAN table. This table stores property set definitions for the boolean property type.
The Primary Key is PROPERTY_META_DATA_ID.
The WLCS_PROP_MD_DATETIME Database Table
Table 2-16 describes the WLCS_PROP_MD_DATETIME table. This table stores property set definitions for the date and time property type.
The Primary Key is PROPERTY_META_DATA_ID.
The WLCS_PROP_MD_FLOAT Database Table
Table 2-17 describes the WLCS_PROP_MD_FLOAT table. This table stores property set definitions for the float property type.
The Primary Key is PROPERTY_META_DATA_ID.
The WLCS_PROP_MD_INTEGER Database Table
Table 2-18 describes the WLCS_PROP_MD_INTEGER table. This table stores property set definitions for the Integer property type.
The Primary Key is PROPERTY_META_DATA_ID.
The WLCS_PROP_MD_TEXT Database Table
Table 2-19 describes the WLCS_PROP_MD_TEXT table. This table stores property set definitions for the text property type.
The Primary Key is PROPERTY_META_DATA_ID.
The WLCS_PROP_MD_USER_DEFINED Database Table
Table 2-20 describes the WLCS_PROP_MD_USER_DEFINED table. This table stores property set definitions for any user defined property type.
The Primary Key is PROPERTY_META_DATA_ID.
The SQL Scripts Used to Create the Database
The database schemas for the WebLogic Personalization Server, WebLogic Commerce Server and BEA's Campaign Manager for WebLogic are all created by executing the create_all script for the target database environment.
Cloudscape
For Cloudscape, execute one of the following:
Oracle
For Oracle, from the command line, move to the following directory:
WL_COMMERCE_HOME/db/oracle/8.1.6
After logging into SQL*Plus, simply execute the create_all.sql script (e.g., @create_all).
SQL Server
For SQL Server, you must first edit the create_all.bat file and properly identify the values for the variables used in identifying the target database environment (for example, user_id, password and server). Once the variables have been set properly, execute create_all.bat from the command line.
Defined Constraints
In each create-catalog-*.sql file, the database tables described earlier in this chapter are created. In addition, the SQL files define constraints.Table 2-21 shows the table name and describes the constraint(s) defined for it.
Note: The sample SQL statements in the attached document table are from the create-catalog-oracle.sql file. The syntax is different for Cloudscape. Except where noted, the index and the effect of each constraint is the same.
![]() |
![]() |
![]() |
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|