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.
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.

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.
- 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

WebSphere Commerce Version 8.0.4.0

Database 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.

The database schema changes are grouped into the following categories:

New tables
Removed tables
Deprecated tables
Tables that include new columns
Tables that include changed columns
Tables that include new or changed indexes
Table relationships that are new or changed

New tables

New tables in this version:

Changed tables

No tables are changed in this version.

Removed tables

No tables are removed in this version.

Deprecated tables

For the list of deprecated database tables, see Deprecated tables and columns.

Tables that include new columns

Columns introduced in this version:

SCHCONFIG.SCCDESCRIPTION

Tables that include changed columns

Columns that are new or changed in this version:

KEYS.TABLENAME - SET DATA TYPE VARCHAR(30)
KEYS.COLUMNNAME - SET DATA TYPE VARCHAR(30)
STAGLOG.STGTABLE - SET DATA TYPE CHAR(30)
STGMERTAB.TABNAME - SET DATA TYPE CHAR(30)
STGMRSTTAB.COLNAME - SET DATA TYPE CHAR(30)
STGMRSTTAB.TABNAME - SET DATA TYPE CHAR(30)
STGSITETAB.TABNAME - SET DATA TYPE CHAR(30)

Tables that include new or changed indexes

Indexes that are new or changed in this version:


Table	Action	Index name	Index	Uniqueness
	Add	I0001551	CATENTRY_ID + CONTENT_ID + CATOVRGRP_ID + LANGUAGE_ID	Unique
	Add	I0001549	CONTENT_ID	Non-unique
	Add	I0001550	CATENTRY_ID	Non-unique
	Add	I0001554	CATGROUP_ID + CONTENT_ID + CATOVRGRP_ID + LANGUAGE_ID	Unique
	Add	I0001552	CONTENT_ID	Non-unique
	Add	I0001553	CATGROUP_ID	Non-unique
	Add	I0001547	TYPE	Non-unique
	Add	I0001548	CONTENT_ID	Non-unique

Table relationships that are new or changed

Table relationships that are new or changed in this version:


Table	Column	Action	Constraint name	Foreign table	Foreign column	Constraint type
	CE_EXTERNAL_CONTENT_REL_ID	Add	P_0054			Primary key
	CONTENT_ID	Add	F_3784		CONTENT_ID	Cascade
	CATENTRY_ID	Add	F_3785	CATENTRY	CATENTRY_ID	Cascade
	TYPE	Add	F_3786		IDENTIFIER
	CG_EXTERNAL_CONTENT_REL_ID	Add	P_0055			Primary key
	CONTENT_ID	Add	F_3787		CONTENT_ID	Cascade
	CATGROUP_ID	Add	F_3788	CATGROUP	CATGROUP_ID	Cascade
	TYPE	Add	F_3789		IDENTIFIER	Cascade
	CONTENT_ID	Add	P_0052			Primary key
	TYPE	Add	F_3782		IDENTIFIER	Cascade
	ASSETNAME, CONTENT_ID	Add	P_0053			Primary key
	CONTENT_ID	Add	F_3783		CONTENT_ID	Cascade
	IDENTIFIER	Add	P_0051			Primary key