WebSphere Commerce Version 8.0.4.0 or later

What's new in Version 8 Mod Pack 4

What's new includes information about new functionality and changes in existing functionality from WebSphere Commerce Version 8 to WebSphere Commerce Version 8 Mod Pack 4.

WebSphere Commerce Version 8.0.4.30

8.0.4.30

With the release of WebSphere Commerce 8.0.4.30, the ability to create an instance using WebSphere Application Server bundled with Java 8 directly is introduced. Prior to this release, there was a limitation in place preventing instances from being created with Java 8 directly. As a result of this change, WebSphere Commerce no longer has any dependencies on Java 7.

This improvement has been tested with latest recommended version of WebSphere Application Server, WebSphere Application Server 8.5.5.24.

Important: To upgrade to WebSphere Commerce or WebSphere Commerce Developer 8.0.4.30 from any previous version, you must first upgrade to 8.0.4.29. This is required due to changes to JAR files that were made due to security vulnerabilities.
To upgrade to WebSphere Application Server 8.5.5.24, you must:
  1. Migrate WebSphere Commerce to Java 8. Ensure that WebSphere Commerce is migrated to Java 8 to align with the requirements of WebSphere Application Server 8.5.5.24 and greater. For more information, see Upgrading WebSphere Commerce 8.0.4.27+ to Java 8.
  2. Remove Java 7 from your WebSphere Commerce environment.

    This is required to maintain compatibility with WebSphere Application Server ​8.5.5.24​ and greater.

  3. Install or upgrade to WebSphere Application Server 8.5.5.24 or greater.
WebSphere Commerce Version 8.0.4.29

8.0.4.29

Important: If you are using Java version 8.0.7.0 to 8.0.7.9, or WebSphere Application Server version 8.5.5.21 to 8.5.5.23, you must lower the priority of the IBMJCEPlus security provider.

Using the com.ibm.crypto.provider.IBMJCEPlus security provider causes a memory leak, leading to performance implications.

  1. Open the jre/lib/security/java.security configuration file for editing in your SDK installation directory.
  2. Change the order of the security providers to place com.ibm.crypto.plus.provider.IBMJCE above com.ibm.crypto.provider.IBMJCEPlus.

    For example, your file should appear as follows:

    security.provider.1=com.ibm.jsse2.IBMJSSEProvider2
    security.provider.2=com.ibm.crypto.plus.provider.IBMJCE
    security.provider.3=com.ibm.crypto.provider.IBMJCEPlus
    security.provider.4=com.ibm.security.jgss.IBMJGSSProvider
  3. Save and close the file.
WebSphere Commerce Version 8.0.4.26

8.0.4.26

Important: The original upload of the 8.0.4.26 fix pack for WebSphere Commerce Developer (8.0.4.26-WS-WCDeveloperEnterprise-ModFixPack.zip, and 8.0.4.26-WS-WCDeveloperProfessional-ModFixPack.zip) included a strict prerequisite check for Java 8 that did not allow for any variation in how it was installed in the environment.

The fix pack has been modified to remove this specific requirement (IBM WebSphere SDK Java Technology Edition 8.0 optional extension offering for IBM WebSphere Application Server 8.5.5.18). Installing IBM WebSphere Application Server v8.5.5.18 or higher fix pack level and Rational Application Developer 9.6 are the only prerequisites that are required for the fix pack.

The updated fix packs can be differentiated by the appended -R in their file names. For example, 8.0.4.26-WS-WCDeveloperEnterprise-ModFixPack-R.zip, and 8.0.4.26-WS-WCDeveloperProfessional-ModFixPack-R.zip.

WebSphere Commerce Version 8.0.4.26

Discontinuation of Java 7 support

Restriction:
  • WebSphere Commerce instance creation is not supported with WebSphere Commerce fix packs that require Java 8 until version 8.0.4.30. If you need to create a new WebSphere Commerce instance, you must use WebSphere Commerce 8.0.4.30 or greater. Alternatively, you can use an older Java 7 fix pack, such as 8.0.4.25, before upgrading to Java 8 and a more recent WebSphere Commerce fix pack.
  • For IBM i OS operating systemNew instance creation is not supported on IBM i.
Important: If you plan to upgrade to WebSphere Commerce version 8.0.4.26, or any subsequent fix pack, you must upgrade your environments accordingly.

For more information on upgrading to WebSphere Commerce 8.0.4.26, see Upgrading to 8.0.4.26 or greater.

WebSphere Commerce Version 8.0.4.26

Important stack updates

Significant updates to companion software for WebSphere Commerce have been made.

The most significant of these updates include:

  • Support for Rational Application Developer version 9.6.

    To upgrade to Rational Application Developer version 9.6, see Upgrading from Rational Application Developer Version 9.5 to Rational Application Developer Version 9.6.

    Rational Application Developer version 9.5 is end of life, and is no longer being supported by IBM.

  • Upgrade to ckeditor version 4.15.1.

    The default version of ckeditor that is included with WebSphere Commerce is being upgraded to a newer version due to a security vulnerability. If you have made any customizations to ckeditor, you must back up the customization, and re-apply it once you have completed the fix pack installation.

For more information on stack updates, see Recommended software, fixes, and settings for WebSphere Commerce Version 8.0.

WebSphere Commerce Version 8.0.4.26

Session invalidation security enhancement

Site user session invalidation has been enhanced.

For more information on session invalidation and the enhancements, see Session invalidation.

WebSphere Commerce Version 8.0.4.24

Account lockout behavior enhancement

Site users can now reset their passwords after hitting the limit of incorrect login attempts. This is facilitated by the Logon command returning a new error code, 2490, instead of disabling the account. Ensure that you update your store login flow to handle this new error code.

WebSphere Commerce Version 8.0.4.3

jQuery Aurora starter store

The Aurora starter store in WebSphere Commerce is completely written in jQuery 3.1.0, which is one of the most commonly used JavaScript libraries used in dynamic websites. The jQuery AJAX and events API provides an easy to use framework that meets most AJAX requirements for storefront development.

In addition to all the existing features that are supported in the Dojo version of the Aurora starter store, the jQuery version supports the following additional capabilities:

  • Store pages load a minimal number of JavaScript and CSS files, as a build script is provided that merges the code from all the files and then generates fewer files, with all its contents combined and minified. This performance strategy improves the web browser's page load time for store pages.
  • A store function is available to control whether dynamic E-Marketing Spots are loaded either server-side with the page, or loaded after the initial page load is complete, to better support Content Delivery Network (CDN) caching.
  • Interactions in the category page are implemented using full page loads, rather than using AJAX. This strategy simplifies page coding and removes the complexity of handling the web browser's back, forward, and bookmark features.
Note: The jQuery Aurora starter store is available to publish as a separate SAR file. It is available in addition to the existing Dojo-based Aurora starter store, not necessarily as a replacement.

For more information, see jQuery Aurora starter store.

Apple Pay on the Web integration

Apple Pay on the Web integration with WebSphere Commerce provides you with an easy and secure way to accept and process payments. Apple Pay on the Web enables customers to purchase products in the Aurora starter store with a single touch in Safari on Mac, iPhone, and iPad.

For more information, see Apple Pay on the Web integration.

Watson Content Hub integration

The Watson Content Hub (formerly DX Content Hub) gives business owners the power to create iconic, robust, and consistent brand experiences by using cloud-based, cognitive content management capabilities. Marketing and merchandising professionals can quickly select content to create relevant offers that are delivered across multiple channels, such as mobile, web-based or email, including those delivered by IBM Watson Campaign Automation and IBM Commerce on Cloud.

For more information, see Watson Content Hub integration.

Tax enhancements

Surcharge tax calculations can be enabled in the Aurora starter store. In some geographic zones, surcharges are added to some products according to local business rules. A surcharge tax results in a new type of tax category. It is required to be collected for some products when surcharges are added to an orders' grand total.

For more information, see Surcharge tax.

Dynamic Pricing integration

You can integrate Dynamic Pricing, a cloud-based pricing system, with WebSphere Commerce, so merchandisers can quickly analyze and react to pricing changes in the market. Pricing data can be automatically exported from WebSphere Commerce to Dynamic Pricing, where the data then is analyzed in relation to business strategies and other sources of market data. Updated prices can be approved and automatically imported to WebSphere Commerce, so the adjusted prices can appear on the live storefront.

For more information, see IBM Dynamic Pricing.

Support for Oracle 12cR2 databases

You can now use Oracle 12cR2 databases in your development and runtime environments. This includes upgrading your database on existing environments and creating instances with new databases.