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.
- 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.
  - Catalog
    - services/Catalog/AttributeDictionaryAttribute/noun.htm
      AttributeDictionaryAttribute noun is used to model an attribute dictionary attribute. An attribute dictionary provides a central place to manage common attributes shared by products.
    - services/Catalog/Catalog/noun.htm
      Catalog noun is used to model a catalog. A catalog can be a primary or a secondary catalog. A catalog represents the contexts under which the catalog groups or catalog entries are defined. When referring to any catalog entity including the Catalog, it is assumed that a store ID is present in the business context. When referring to a catalog entry, catalog group or a kit, the catalog ID is assumed to be present in a catalog context.
    - services/Catalog/CatalogEntry/noun.htm
      CatalogEntry noun is used to model a catalog entry. A catalog entry can be a product, an item, a package, kit or a bundle. The catalog ID, store ID and language are assumed to be set in the business contexts. The entitlement context is required for retrieving the offer prices. CatalogEntry noun is used by the Catalogs Tool at authoring time, and the store front at runtime.
    - services/Catalog/CatalogFilter/noun.htm
      The CatalogFilter noun defines types related to a catalog filter. A catalog filter contains the information to filter the categories and products within a catalog based on static inclusions or exclusions and dynamic conditions that are based the properties or attributes of products.
    - services/Catalog/CatalogGroup/noun.htm
      CatalogGroup noun is used to model a catalog group (or category). A catalog group represents a node in a catalog hierarchy or a tree. A node has a parent and can have zero or more child catalog groups or catalog entries. CatalogGroup noun is used by the Catalogs Tool at authoring time, and the store front at runtime. BOD Summary
    - services/Catalog/CatalogNavigationView/noun.htm
      The CatalogNavigationView noun was created to represent all of the information that is required to make use of faceted navigation (from a search engine) when a shopper is browsing catalog pages for a store model (Aurora) that is provided by default.
  - Content
  - Contract
  - Gift Center
  - Infrastructure
  - Installment
  - Inventory
  - Location
  - Marketing
  - Member
  - Order
  - Page Layout
  - Price
  - Promotion
  - Search
  - Store
  - Subscription
  - Wallet
  - WebSphere Commerce WSDL files
    WebSphere Commerce provides WSDL files to describe its 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

Catalog