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
    - services/Member/MemberGroup/noun.htm
      The MemberGroup noun defines types related to a member group. A member group is a group of persons or organizations. A member group can be used for different purposes. The purpose is specified using the usage. Currently the only usage that is supported is GeneralPurpose.
    - services/Member/Organization/noun.htm
      The Organization noun defines types related to an organization. The service data object (SDO) is com.ibm.commerce.member.facade.datatypes.OrganizationType.
    - services/Member/Person/noun.htm
      The Person noun defines types related to a person. A person is a human that can be a guest, a registered user or an administrator. The service data object (SDO) is com.ibm.commerce.member.facade.datatypes.PersonType. BOD Summary
    - Member component client library
      The member client library class, MemberFacadeClient, contains Web-friendly methods to facilitate calling various operations.
    - Mapping of member logical schema to command parameters and database columns
      The following sections detail how the logical schema (nouns) of the member subsystem relate to specific command parameters and database columns.
    - Member component message mapper configuration
      The member component uses the message mapper infrastructure to determine which WebSphere Commerce command to call based on the request BOD. The message mapper infrastructure provides a way to flatten the values in the SDO noun into name-value pairs that the WebSphere Commerce command can process.
    - Member services: get-data-config.xml file
      XML Schema Documentation: get-data-config.xml file
  - 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

Member