Product overview > What's new summary


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 v6 and a different value in WebSphere Commerce v7.


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 change flow options to accommodate a variety of flows, depending on customer needs.

In WebSphere Commerce v7, 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 v7 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.

For more information, see http://www-01.ibm.com/support/docview.wss?uid=swg21303827 and 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 v6 Oracle database, migrate the database character set to use AL32UTF8.


Order trash can feature disabled by default

In WebSphere Commerce v7, the order trash can feature is disabled by default. In WebSphere Commerce v6, the default owner for deleted orders was -1002. In v7, the default owner for deleted orders is now -1006 (a guest user).


Related concepts

Fix pack summary

Highlights of v7

New features and functionality

Deprecated functionality

Discontinued functionality

User experience and documentation changes

WebSphere Commerce now uses the DB2 JCC type 4 connection type


Related tasks

Configure deleting order items and requisition lists

Related reference

Prerequisites for installing WebSphere Commerce


+

Search Tips   |   Advanced Search