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
  - Content
  - Contract
  - Gift Center
  - Infrastructure
  - Installment
  - Inventory
  - Location
  - Marketing
  - Member
  - Order
  - Page Layout
    - services/PageLayout/Layout/noun.htm
      The Layout noun is used to model a layout, which can be applied to a particular page. This noun is used for authoring purposes only and is not used in the store. A Layout noun is composed of a description, schedule, page locations, widgets, and widget configuration properties. Each layout belongs to one store, one device classification, and one layout group(also referred to as page type). A layout has a state ('Active', 'InActive', 'MarkForDelete') and specifies whether it is considered a template for creating new layouts, or it is a completed layout.
    - services/PageLayout/Page/noun.htm
      The Page noun is used to represent a URL (or page) on a site. A page contains information such as an administrative name, a page URL and SEO meta properties.
    - services/PageLayout/PageDesign/noun.htm
      The Page Design noun represents the layout of a page in a storefront. This noun is used in the store and contains only information that is needed by the store to draw the page layout. BOD Summary
    - services/PageLayout/WidgetDefinition/noun.htm
      A WidgetDefinition represents a widget (or component) that can be placed on a page layout. WidgetDefinition's are registered on a system and each store can subscribe to using any of them. This noun describes the definition (or registration) of the widget itself and not the application of it to a layout. A widget definition describes a widget on the system including a name, description, vendor, state, JSP path, properties, definition XML and other properties. This noun is used for authoring and store purposes to retrieve data only.
  - 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

Page Layout