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
    - services/Marketing/Activity/noun.htm
      The Activity noun is used to model a marketing activity. Marketing activities allow you to define the marketing messages to deliver to customers when a given activity is triggered. BOD Summary
    - services/Marketing/Campaign/noun.htm
      The Campaign noun is used to model a marketing campaign. Campaigns serve to organize your marketing efforts. Campaigns contain any number of marketing activities, which are classified as either Web activities, or e-mail activities. BOD Summary
    - services/Marketing/CampaignElementTemplate/noun.htm
      The CampaignElementTemplate noun is used to model a campaign element template. Campaign element templates are the template definitions of elements within a marketing campaign. BOD Summary
    - services/Marketing/MarketingContent/noun.htm
      The MarketingContent noun is used to model marketing content. Marketing content refers to any creative material created for your site. Marketing content can have multiple language descriptions, and can optionally be associated with an attachment. BOD Summary
    - services/Marketing/MarketingEmailTemplate/noun.htm
      The MarketingEmailTemplate noun is used to model a marketing e-mail template. A marketing e-mail template defines the subject and content of the e-mail. The templates are capable of providing robust, dynamic, and personalized e-mail messages.
    - services/Marketing/MarketingSpot/noun.htm
      The MarketingSpot noun is used to model an e-Marketing Spot. An e-Marketing Spot reserves space on your store pages in which personalized marketing content displays. This noun is used in an authoring environment to provide the list of e-Marketing Spots when creating marketing activities, and to manage creating, updating and deleting e-Marketing Spots. In the storefront, the MarketingSpotData noun is used to provide the data to display to customers in an e-Marketing Spot. BOD Summary
    - services/Marketing/MarketingSpotData/noun.htm
      The MarketingSpotData noun is used to model e-Marketing Spot data. This is the data to display to a customer in an e-Marketing Spot. The e-Marketing Spot data contains the catalog entries, catalog groups, and marketing content to display in the storefront. The corresponding campaign, activity, and experiment test element information are returned with each data element. This noun is used in the storefront to provide the data to display to customers in an e-Marketing Spot. In an authoring environment, the MarketingSpot noun is used to list and manage e-Marketing Spots when creating marketing activities.
    - services/Marketing/MarketingTrigger/noun.htm
      The MarketingTrigger noun is used to model a marketing trigger. Marketing triggers are used to communicate with the marketing runtime that particular events have occurred (customer interaction points that start or continue a marketing activity), or that the marketing runtime should perform a specific action.
  - 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

Marketing