Changed functionality

Changed functionality typically involves changes in default values or an outcome different from what 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.

Feature Pack 5 or later

Starter stores

  • The Aurora starter store replaces the Madisons starter store used in the previous release.
  • The following starter stores not available to the Publish wizard or publishstore utility by default:
    • Madisons.sar
    • Madisons-enhancements.sar
    • SocialCommerce.sar
    • MadisonsStorefrontAssetStore.sar
    • Feature Pack 6 or laterMadisonsMobileEnhancements.sar
    • Feature Pack 6 or laterMadisonsTablet.sar
    To use these SAR files, see Displaying additional stores
  • The Brazil starter store is now packaged as a stand-alone store archive. In previous feature packs it was necessary to publish the Madisons store archive; then publish the Brazil store archive on top of Madisons. This step is no longer required.
  • The MayUJoy starter store is now packaged as a stand-alone store archive. In previous feature packs it was necessary to publish the Madisons store archive; then publish the MayUJoy store archive on top of Madisons. This step is no longer required.
Feature Pack 5 or later

IBM Management Center for WebSphere Commerce

Workspaces has new capabilities and improved functionality with change history. Prior to moving to feature pack 5, ensure that you have no in-progress workspaces. Approve all content before moving to the feature pack.

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 stand-alone store with 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.

Note: The IBM Sales Center does not support pickup in-store capabilities. If an order is created in the Madisons starter store, with the shipping mode as pickup in-store, the order can be opened in Sales Center in read-only mode. It is not available for editing.

Apache Derby replaces Cloudscape database support

WebSphere Commerce Version 7 supports Apache Derby instead of Cloudscape. IBM no longer supports 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 IBM Cloudscape Referral Page and Apache Derby.

DB2 loop-back configuration is removed on Unix platforms

DB2 loop-back configuration is removed from UNIX platforms. The DB2 loop-back configuration was implemented as a workaround due to a DB2 limitation. This limitation is resolved with the new DB2 JCC type 4 connection type.

Oracle database character set is changed from UTF8 to AL32UTF8

WebSphere Commerce is moving 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.

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).