wcs

10 Steps to Configure Email – Websphere Commerce Server Websphere Commerce Server – Configure Email Follow 10 steps for configuring email in Websphere Commerce Server Step 1: Create a JSP ( eg:- AbcEmailNotify.jsp) Create a JSP, lets name it AbcEmailNotify.jsp AbcEmailNotify.jsp will be used for displaying contents of email to recipient. Note: Currently keep AbcEmailNotify.jsp as blank (without any code) Step 2: Create View ( eg- AbcEmailNotifyView) Make an Entry in Struts-Config.xml file for AbcEmailNotify.jsp as below < action path=’/AbcEmailNotifyView’ type=’com.ibm.commerce.struts.BaseAction’> < set-property property =’authenticate’ value =’10101:1′/> < set-property property =’https’ value =’10101:1′/> < /action> < forward name=”AbcEmailNotifyView /10101/-3″ path=”/< location of JSP file >/AbcEmailNotify.jsp” className=”com.ibm.commerce.struts.ECActionForward”> < set-property property=”implClassName” value=”com.i...

This method searches the command registry( CMDREG table) for an entry corresponding to the specified command name (Interface)and storeId. if no entry is found for specified store, it will look for an entry corresponding to storeId=0. if both fail, it will check for a default implementation of the command from the interface and returns an entry that represent the default implementation of the interface. Ex: static final String defaultCommandClassName = "com.ibm.commerce.sample.commands.MyNewControllerCmdImpl"; so, when you make a command with the CommandFactory class, you need to pass in the interface name, rather than the implementation class, since the field looked up in the database is the CMDREG.INTERFACE field. if you specify the implementation class ( MyNewControllerCmdImpl ) rather than the interface ( MyNewControllerCmd ) may result in a ClassNotFoundException.

Catalog The catalog subsystem is a component of the WebSphere Commerce Server that provides online catalog navigation, partitioning, categorization, and associations. In addition, the catalog subsystem includes support for personalized interest lists and custom catalog display pages. The catalog subsystem contains all logic and data relevant to an online catalog, including catalog groups (or categories), catalog entries, and any associations or relationships among them About Master Catalog: The master catalog is the central location to manage your store's merchandise. Everything you need in your store is contained within the master catalog. It is the single catalog containing all products, items, relationships, and standard prices for everything that is for sale in your store You can share the master catalog across stores and define as many stores as needed. About Sales Catalog A sales catalog is a subset of the merchandise and services found in the master catalog. A sales catalog ...

1.For promotions and espot confirgurations, which is a better approach - management centre or accelerator? Considering the management centre's design, its complex structure takes more time in implementing new modifications as compared to accelerator modifications. 2. We can view the status what we did change in MC,If we did any wrong it's show error,but in acceleration not showing any error. 3. Management center provides a rich UI with features like drag and drop. There is a possibility that in some future release commerce Accelerator may be removed. With current release it is not possible as it is tightly coupled with the framework. For a end user perspective Management Center will be the preferred tool. Being a flash based tool it is slow but very user friendly. 4. Management Centre, It is sometimes slow but it provides more usuability such and drag drops etc which makes it a fav tool for the business user.

Feature packs include new features & add new functionality to improve your WebSphere Commerce solution. The feature pack differs from a fix pack in that it does not contain fixes to the base WebSphere Commerce product.

Order trash can feature disabled by default In WebSphere Commerce Version 7, the order trash can feature is disabled by default. In WebSphere Commerce Version 6, the default owner for deleted orders was -1002. In Version 7, the default owner for deleted orders is now -1006 (a guest user). Changed functionality Changed functionality typically involves changes in default values or an outcome different from what would have occurred in previous releases. For example, a default parameter might use one value in WebSphere Commerce Version 6 and a different value in WebSphere Commerce Version 7. Madisons starter store replaces the consumer direct sample store The Madisons starter store is the new store that replaces the consumer direct sample store in the previous release. The Madisons starter store uses Rich Internet Application (RIA) technologies such as Asynchronous JavaScript and XML (AJAX) and Dojo widgets to provide customers with an interactive and rich shopping experience. RIA technolo...

eSpots(e-Marketing Spots) ESpots are specific defined areas on a JSP page whose content can be dynamically configured based on rules. eSpots reserve space on your store pages in which content displays. Use for marketing activity. Add email activity (send promotional mails for selected group in specified time), web activity(start,end date,priority,status). For calling e-marketing spot use below jsp c-Spots (Content Spot ) -atleast one content is mandatory - -can be scheduled with start/end date -call the content spot name in jsp to display the attached content For calling c-spot use below jsp