WebSphere Commerce shopping flow URLs are organized by subsystem.
The Order Management subsystem includes all logic and data relevant to placing, processing, and managing orders. The Order Management subsystem also deals with returns.
The following URLs are related to order fulfillment:
Data beans are grouped into several component groups.
URL commands, controller commands, task commands, view commands and tables are related to each other.
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.
Legacy API classes can be browsed via Javadoc. New API classes are exposed using the REST interface.
Catalog subsystem URLs include all logic and data relevant to a catalog, including categories, products and their attributes, items, and groupings of each, and any associations or relationships among them.
Each IBM Gift Center action is a Struts action that calls the service interface for the gift registry to perform a requested action. If you are developing a store using the gift registry feature (for example, creating JSP files), you should be familiar with the actions. The actions are executed from a browser.
The Marketing subsystem includes all logic and data relevant to marketing concepts for your site, such as campaigns, Web activities, customer segments, email activities, and collaboration.
The Member subsystem includes all logic and data relevant to registration, authentication, and grouping of all members. A member can be a user, an organization or organizational entity, or a member group.
The following URLs relate to the Messaging system.
Several order URLs accept order abbreviations such as "*" and "." to indicate one or more values for some of their parameters that specify order identifiers. URLs that accept order abbreviations generally accept any of the following abbreviations, although "**" and ".**." (which involve creating a new order) may not be applicable for some URLs. Refer to each URL's documentation to understand which abbreviations are accepted by each URL. Many URLs accept the following order abbreviations for parameters that specify order reference numbers.
A diagram showing various scenarios including the service calls, optional commands, controller commands and views.
The four diagrams are comprised of one overall view and three simplified diagrams each showing a particular flow process. The status transition in each shopping flow diagram applies to all business models.
The Order Management subsystem uses many task commands. Each task command performs one function.
The following URLS are related to orders:
The following URLs are related to order items:
This URL changes the assigned fulfillment center if the one specified is different from the one originally assigned, and it releases the order items. One or more releases can be created from the selected order items. (A release is a set of products in a given order that have the same ship-to address, fulfillment center, and shipping carrier.)
This command updates expected inventory records to synchronize with a backend system. It works by attempting to find the RADETAIL and RA records based on the primary key or unique index for each (see RA and RADETAIL table definitions). If a record can be found, it is updated with the values specified in the parameters. If a record cannot be found, the command attempts to create a new record using the values specified in the parameters. This command cannot be used to update or insert into the RA table only. It must be used to update both the RA and RADETAIL tables or only the RADETAIL table.
The following URLs are related to order quotations:
The following URLs are related to order payment.
The following URLs are related to Returns and refunds.
The following URLs are related to scheduled orders:
The following URL is related to currency.
A requisition list is a list of items that is used to create orders at a later date. Users can create requisition lists of items that they order frequently and use it to periodically re-order the items. Each item on a requisition list is associated with a catalog entry and has the following attributes: SKU, Quantity, Last update time, Owner, Store, Type: private or shared. Private requisition lists can be viewed and modified only by a certain user, typically the creator. A shared requisition list can be read and used by the users in the same organization.
The Trading subsystem includes all logic and data relevant to negotiating or determining the price and associated quantity of an individual product or set of products. In particular, this area deals with the auctioning of goods and services, contracts, and RFQs (Requests for quotes).
The server subsystem consists of functions that are associated with URLs that are run by the scheduler.
The starter stores consist of pages that are associated with URLs that are run by WebSphere Commerce search. You can use the following URLs to invoke various WebSphere Commerce search tasks.
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.
Any given database data model displays the relationship among database tables in the schema.
During installation, WebSphere Commerce sets up the caching system with the default values.
The root element of the cachespec.xml file, <cache>, contains <cache-entry> elements. The WebSphere dynamic cache service parses the cachespec.xml file during startup, and extracts a set of configuration parameters from each <cache-entry> element.
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.
The extension points listed on this page are provided by IBM and used in the IBM Sales Center.
WebSphere Commerce REST services are JAX-RS REST services that are built on top of Apache Wink. The implementation classes contain JAX-RS annotations such as @Path, @Produces, @Consumes, @QueryParam, and @PathParam.
In WebSphere Commerce Version 6.x the Payments subsystem was introduced. Payment processing using the WebSphere Commerce Multipayment Framework (used in version 5.x) and payment processing using the Payments subsystem is fundamentally different.
Parameters for the commands described here apply to the framework only. Note that in most cases, WebSphere Commerce Payments does not check for duplicate parameters. If more than one instance of a parameter is specified, then the last instance will be used.
The Data Load utility contains several configuration files. You can use the configuration file schema to understand and customize the data load configuration files.