WCS

Data Bean A data bean is a java bean that is used within a jsp page to provide dynamic contect to the jsp page. A data bean normally provides a simple representaion of a WebSphere Commerce Entity bean. There are 3 types of data beans:  1.Smart databean.  2.Command databean  3. Input data bean Smart data bean: When a smart data bean is activated, the data bean manager invokes the data bean's populate method. Using the populate method, the data bean can retrieve all attributes, except attributes from associated objects. Command data bean: A data bean implementing the CommandDataBean interface retrieves data from a data bean command. A data bean of this type is a lightweight object; it relies on a data bean command to populate its data. The data bean must implement the getCommandInterfaceName() method which returns the interface name of the data bean command. Input data bean: A data bean implementing the InputDataBean interface retrieves data from the URL parameters or attri

Important Commands & DataBeans present in Catalog Subsystem Commands-- StoreCatalogDisplayCmdImpl- This command sets the view task that will display the Catalogs available to browse in the current Store. TopCategoriesDisplayImpl- This command sets the view task that will display the root Categories in a specified Catalog. CategoryDisplayCmdImpl- retrieves the configured display page for the specified category in the specified catalog. ErrorMissingAttributeCmd- This error task command is set when a Product to Item resolution fails due to missing product attributes. ErrorProductAttributeCmd- This error task command is set when a Product to Item resolution fails due to incorrect product attributes ProductDisplayCmdImpl- This command retrieves the configured Display Page for the specified CatalogEntry which will in turn be launched in order to display information about the CatalogEntry.This command first ensures that the CatalogEntry specified by

ORDER SUBSYSTEM Order Sub-system is a component of WCS that provides shopping carts, order capture, order fulfillment, inventory & payment function support. An order includes one or more products, billing & shipping addresses, payment details & the total cost including shipping charges   & taxes. From a customer persective an order is a list of selected products. Each product in a list is called an order item. From a store perspective an order is a list of order items. Orders are associated with a single store. An order profile is a special type of order that can be associated with either a store or a store group. The order profile holds default information about a customer such as payment information, shipping address, shipping mode & billing address. Ø   There are 4 inventory systems, they are: 1.   ATP inventory. 2.   Non-ATP inventory. 3.   No inventory. 4.   External inventory. ATP Inventory:  The ATP inventory model enables

Types of SUBSYSTEMS IN WCS. Catalog Subsystem. Order Subsystem. Trading Subsystem. Merchandising Subsystem. Marketing Subsystem. Member Subsystem. Payment Subsystem.

Some Basics on Order subsystem WCS Ordering Process In IBM WCS both cart and orders are managed in the same table for a user, a cart transitions through various states and this is used to identify the cart state. For example a pending order would have orders.state as "P", while a submitted order will have ORDERS.state as "M" Review following link for more information on Order state transition http://publib.boulder.ibm.com/infocenter/wchelp/v7r0m0/topic/com.ibm.commerce.developer.doc/refs/rosordstattran.htm In general checkout flow supports both AJAX and non AJAX version of server side processing, review AJAX URL's defined in following OOB Struts configuration files for supported AJAX actions /Stores.war/WEB-INF/struts-config-order-services.xml has all the AJAX versions of the command defined in it. 1. Add to Cart: User is browsing the site as anonymous, guest or authenticated user and adds an item from browse pages to cart You can call the OOB non