WebSphere Commerce shopping flow URLs are organized by subsystem.
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).
WebSphere Commerce supports the following auction URLs:
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.
The Order Management subsystem includes all logic and data relevant to placing, processing, and managing orders. The Order Management subsystem also deals with returns.
Generates a unique autobid reference number and displays a page for autobid submission after ensuring that the customer is authorized to bid.
Validates input from the AutoBidCreateForm and AutoBidUpdateForm commands.
Provides the customer with an autobid modification page, populated with the current values corresponding to the autobid to be modified.
Allows customers to withdraw autobids they have submitted for Open Cry auctions.
Generates a unique bid reference number and displays a bid creation page after ensuring that the customer is authorized to bid.
Allows customers to withdraw bids they have submitted in an auction.
Validates input from the BidCreateForm command or the BidUpdateForm command.
Provides the customer with a bid modification page, populated with the current values corresponding to the bid to be modified.
Closes the auction for all bids.
Marks one or more messages in the MSGMEMREL table for deletion.
Displays the rules associated with a particular auction. All bidders must view the rules once before bidding.
Displays a message from the MESSAGE table. The messages are created by the Trading subsystem.
Displays the product display template for an auction.
Invoked by the WebSphere Commerce scheduler to process pending auction notifications. Notifies bidders using the configured messaging system. No display page will return.
Invoked by the scheduler to retrieve all auctions with a status of Bidding Closed and determine the winners of Open Cry and Sealed Bid auctions. This URL is called by scheduler. No display page will return.
Removes an auction from the customer's auction gallery.
The ModifyForumMessage command is used to delete forum messages or change the view status from private to public.
Invoked by the WebSphere Commerce scheduler every minute to start and close auctions. It checks future auctions to determine if they should be started, checks current auctions to determine if it is time to close the bidding, and closes 'Bidding Closed' auctions. This URL is called by scheduler. No display page will return.
Invoked by the WebSphere Commerce scheduler every minute to process pending auto bids. This URL is called by scheduler. No display page will return.
Invoked by the WebSphere Commerce scheduler every minute to process pending Dutch bids. This URL is called by scheduler. No display page will return.
Invoked by the WebSphere Commerce scheduler every minute to process pending open cry bids. This URL is called by scheduler. No display page will return.
Creates a customer message by inserting a row into the FORUMMSG table.
Updates the MEMBRAUCT table with the specified customer-auction relation types (auction-in-gallery, customer-has-viewed-rules).
Invoked by the scheduler to retrieve all winning bids at site and creates order for each bid.
A Request for Quote (RFQ) is a type of trading mechanism available in WebSphere Commerce. You can maintain and administer RFQs using the WebSphere Commerce Accelerator. When you publish the Deprecated featureadvanced B2B direct starter store provided with WebSphere Commerce, you get the RFQ request tool.
The trading subsystem provides URLs for accounts, contracts and policies.
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.
