Skip to main content

Difference between WCS 6 & WCS 7

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 technologies help to improve order conversion rates and reduce shopping cart abandonment. The store can be used as a standalone store using the consumer direct business model or as an asset store in Extended Sites or Demand Chain business models.
The Madisons starter store provides all the pages and features necessary for a functioning consumer direct online store. It is packaged with WebSphere Commerce as a store archive. It contains a full set of consumer direct features, including user registration, catalog browsing, promotions, and targeted marketing. The store contains rich interactions, including the product quick info pop-up window, product fast finder, mini shopping cart, and a streamlined checkout flow.
The store is fully accessible and translated into group one languages, supporting locale-specific bidirectional languages. Technological features include search engine optimization, support for multiple Web browsers and platforms, and options to accommodate a variety of flows, depending on customer needs.
In WebSphere Commerce Version 7, the Madisons starter store includes the store locator, inventory availability, and buy online, pickup in-store capabilities.

Apache Derby replaces Cloudscape database support:

WebSphere Commerce Version 7 supports Apache Derby instead of Cloudscape. IBM has dropped support for the Cloudscape database. If you are using IBM Cloudscape it is recommended that you upgrade to the recent release of Apache Derby.
DB2 loop-back configuration has been removed on Unix platforms
DB2 loop-back configuration has been removed from Unix platforms. The DB2 loop-back configuration was implemented as a workaround due to a DB2 limitation. This limitation has been resolved with the new DB2 JCC type 4 connection type.
Oracle database character set has been changed from UTF8 to AL32UTF8
WebSphere Commerce has moved to the AL32UTF8 character set to align with the Oracle database recommendations. If you are using a WebSphere Commerce Version 6 Oracle database, you must migrate your database character set to use AL32UTF8.

Workspace Administration Tool:

The Workspace Administration tool is deprecated for WebSphere Commerce Version 7 Feature Pack 3. This feature was used to manage workspaces and workspace-related activities.
Recommended action:
The Workspace Management tool, replaces all of the workspace management features in the Workspace Administration Tool. It is recommended that you use the Assets tool in the Management Center to manage your workspaces. However, if you have business reasons to continue using the Workspace Administration Tool, you can re-enable it. 

Comments

Popular posts from this blog

How to read applied promotions codes

The below snippet will give you to read the promotions codes which are applied to order number, String orderId = "978593958"; OrderKey orderKey = new OrderKey(new Long(orderId)); PromotionArgumentSessionBeanPersistenceManager promoManager = new PromotionArgumentSessionBeanPersistenceManager(); PromotionArgument promArg = promoManager.load(orderKey); Iterator prmoExeRecds = promArg.getPromotionExecutionRecords(); while(prmoExeRecds.hasNext()) { PromotionExecutionRecord promotionExeecutionRecord = (PromotionExecutionRecord) prmoExeRecds.next(); Promotion promotion = promotionExeecutionRecord.getPromotion(); System.out.println("Name: " + promotion.getName()); System.out.println("Admin description: " + promotion.getDescription(commandContext.getLocale(), com.ibm.commerce.marketing.promotion.Description.SHOPPER_SHORT_DESC)); }

How to do Email Configurations in Web sphere Commerce

Web sphere commerce allows to send email messages to customers by making use of the below mentioned steps. Create the JSP which will be used for generating contents of the email  For e.g.: SendEmail.jsp Create View for the JSP in Struts-Config-Ext.xml Make an Entry in Struts-Config-Ext.xml file for .jsp as below < action path='/SendEmailView' type='com.ibm.commerce.struts.BaseAction'>     < set-property property ='authenticate' value ='10001:1'/>      < set-property property ='https' value ='10001:1'/> < /action> < forward name="SendEmailView /10001/-3" path="/< location of JSP file >/ TestEmail.jsp" className="com.ibm.commerce.struts.ECActionForward">     < set-property property="implClassName"     value="com.ibm.commerce.messaging.viewcommands.MessagingViewCommandImpl"/>     < set-property property="int

IBM Announces version 9 of WebSphere Commerce!

What’s new in Version 9 includes information about new functionality and changes in existing functionality from previous WebSphere Commerce Version to the modernized WebSphere Commerce Version 9 release: Micro services architecture , with lightweight, self-contained, distributed servers, supports horizontal scaling, parallel development, and utilization of modern, open source tools. Docker containers deliver key benefits for DevOps , including deployment automation, delivery acceleration, and application portability. Flexible deployment options for  Docker containers  gives IT organizations more infrastructure choices for e-commerce workloads, including all cloud options: private, public, or hybrid deployment. Evolution of the technology stacks  makes customization of the brand and business user experience more efficient and cost effective. Key changes include adoption of lightweight IBM WebSphere Liberty, replacement of Enterprise JavaBeans™ (EJBs) with Java™ Persistence API (J