Home
Reference
WebSphere Commerce database schema
The WebSphere Commerce database model was designed for data integrity and optimal performance. WebSphere Commerce provides several hundred tables that store WebSphere Commerce instance data. To maintain data integrity, and to ease maintenance referential integrity, constraints are widely used in the database model. Indexes are used carefully on tables to avoid over-indexing and to provide a good balance between data retrieval and data manipulation activities (insert and update). The business rules are implemented at the application level rather than by using database trigger. Triggers, however, are used to facilitate data staging and optimistic locking. A limited number of SQL-based database stored procedures are used for data intensive activities.
Data models
Any given database data model displays the relationship among database tables in the schema.
Payment
The payment data models show the database tables that are related to the payments subsystem.
Payments subsystem
The Payments subsystem data model shows the relationship between database tables that contain information about the components that make up the Payments subsystem. These components store the information to determine how payments are handled by the Payment Rule Engine or the Payment Plug-in Controller module.

Reference
- WebSphere Commerce API reference
  WebSphere Commerce exposes two main programming APIs. The first and newest API is a REST interface, and most new classes are exposed here. The legacy Java API also contains new classes not suitable for REST, and can be browsed in Javadoc format.
- Cross-reference of data beans, EJB beans, and tables
  Data beans are grouped into several component groups.
- Cross-reference of commands, tasks, and tables
  URL commands, controller commands, task commands, view commands and tables are related to each other.
- Cross reference: Commands to beans to database tables
  Use this information when you are customizing a command and you want to know which tables are affected. You should also use this topic if you are modifying a table and want to know which commands and beans are affected.
- API changes between WebSphere Commerce Version 7.0.0.9 and WebSphere Commerce Version 8.0.0.0
  If you are migrating version 7.0 of WebSphere Commerce, review the API changes between releases.
- WebSphere Commerce database schema
  The WebSphere Commerce database model was designed for data integrity and optimal performance. WebSphere Commerce provides several hundred tables that store WebSphere Commerce instance data. To maintain data integrity, and to ease maintenance referential integrity, constraints are widely used in the database model. Indexes are used carefully on tables to avoid over-indexing and to provide a good balance between data retrieval and data manipulation activities (insert and update). The business rules are implemented at the application level rather than by using database trigger. Triggers, however, are used to facilitate data staging and optimistic locking. A limited number of SQL-based database stored procedures are used for data intensive activities.
  - Column data type considerations
    Several column data types are available for you to use when you are creating new database table or columns.
  - Schema changes from Version 8 to Version 8 Mod Pack 4
    Database tables and columns within the WebSphere Commerce Version 8 Mod Pack 4 database schema can differ from the tables and columns in the database schema for WebSphere Commerce Version 8.
  - Schema changes from Version 8 to Version 8 Mod Pack 3
    Database tables and columns within the WebSphere Commerce Version 8 Mod Pack 3 database schema can differ from the tables and columns in the database schema for WebSphere Commerce Version 8.
  - Schema changes from Version 8.0.1.0 to 8.0.2.0
    Database tables and columns within the WebSphere Commerce Version 8.0.1.0 database schema can differ from the tables and columns in the database schema for WebSphere Commerce Version 8.0.2.0.
  - Schema changes from Version 8 to Version 8 Mod Pack 1
    Database tables and columns within the WebSphere Commerce Version 8 Mod Pack 1 database schema can differ from the tables and columns in the database schema for WebSphere Commerce Version 8.
  - Schema changes from Version 7 to Version 8
    Database tables and columns within the WebSphere Commerce Version 8.0 database schema can differ from the tables and columns in the database schema for WebSphere Commerce Version 7.
  - Deprecated tables and columns
    If a database table or column is marked as deprecated, then the table or column is outdated by newer constructs. Deprecated sections are supported for reasons of compatibility with an earlier version only. These tables or columns are obsolete or can become obsolete in future versions of WebSphere Commerce.
  - Data models
    Any given database data model displays the relationship among database tables in the schema.
    - Legend for data models
      Database tables within the WebSphere Commerce database schema are organized into functional groups, called data models.
    - Catalog
      The catalog data model shows the relationship between database tables related to the Catalog subsystem.
    - Marketing
      The marketing data model shows the relationship between database tables related to the Marketing subsystem.
    - Promotions
      The promotions data models show the relationship between database tables that are related to the promotions.
    - Member
      The member data model shows the relationship between database tables related to the Member subsystem.
    - Order Management
      The order management data model shows the relationship between database tables related to the Order Management subsystem.
    - Payment
      The payment data models show the database tables that are related to the payments subsystem.
      - Payments subsystem
        The Payments subsystem data model shows the relationship between database tables that contain information about the components that make up the Payments subsystem. These components store the information to determine how payments are handled by the Payment Rule Engine or the Payment Plug-in Controller module.
      - Payment batch
        The Payment batch data model shows the relationship between database tables that contain information about handling batch processing of payments.
      - Payment merchant support
        The Payment merchant support data model shows the relationship between database tables that contain information about payment merchant support. Merchant information is used by the payment side to facilitate payment operation and management.
      - Payment processing
        The Payment processing data model shows the relationship between database tables that contain information about payment processing. The database tables in this data model store information about how to process payment instructions and transactions during the validation, reservation, and finalization stages.
      - Payment rules
        The Payment rules data model shows the relationship between database tables that contain information about payment rules. Payment rules determine which action to take based on the payment instruction, payment method, and the payment event.
    - Store
      The store data models show the relationship between database tables that are related to stores.
    - System
      The system data models show the relationship of database tables used for WebSphere Commerce system functions.
    - Trading
      The trading data models show the relationship of database tables in the Trading subsystem.
    - Content Management
      The Content Management shows the relationship between database tables that contain information about content management.
    - Content management system integration
      The content management system integration data model shows the relationship between database tables used by the solution.
    - Content versioning
      The content versioning data model shows the relationship between database tables that contain information about the content versioning.
    - Folder data model
      The folder data model shows the relationship between the database tables that include information about folder and folder items.
    - IBM Gift Center
      The IBM Gift Center data model shows the relationship between database tables that contain information about IBM Gift Center.
    - WebSphere Commerce search engine optimization
      The WebSphere Commerce search engine optimization (SEO) shows the relationship between database tables that contain information about WebSphere Commerce search engine optimization (SEO).
    - WebSphere Commerce search data model
      The WebSphere Commerce search data model shows the relationship between database tables that are related to WebSphere Commerce search.
- Payments subsystem
  In WebSphere Commerce, payment processing uses the Payments subsystem.
- Dynamic caching
  In general, caching improves response time and reduces system load. Caching techniques are used to improve the performance of World Wide Web Internet applications. Most techniques cache static content (content that rarely changes) such as graphic and text files. However, many websites serve dynamic content, containing personalized information or data that changes more frequently. Caching dynamic content requires more sophisticated caching techniques, such as those provided by the WebSphere Application Server dynamic cache, a built-in service for caching and serving dynamic content.
- Data Load utility configuration file schema
  The Data Load utility contains several configuration files. You can use the configuration file schema to understand and customize the data load configuration files.
- WebSphere Commerce web services
  WebSphere Commerce provides many web services.
- Utilities
  Utilities help you to accomplish administrative or configuration tasks, for example, loading data, publishing a store.
- Shopping flow URLs
  WebSphere Commerce shopping flow URLs are organized by subsystem.
- Ant targets
  A WebSphere Commerce instance can be created from the command line. The command-line utility uses Apache Ant to create the objects required. The targets are divided into several high-level groups that correspond to the environment that is to be configured.
- Glossary

Payments subsystem data model

The Payments subsystem data model shows the relationship between database tables that contain information about the components that make up the Payments subsystem. These components store the information to determine how payments are handled by the Payment Rule Engine or the Payment Plug-in Controller module.

The data in database tables with prefix "EDP" is manipulated by the Payment Rule Engine module in the Payments subsystem. The Payment Plug-in Controller module in Payments subsystem manipulates the data in database tables that are prefixed with "PPC". For more information about each table, click that table.