Recommended fixes and settings for WebSphere Commerce Version 7

This topic provides a comprehensive list of recommended, generally available (GA) fixes for IBM WebSphere Commerce Version 7 releases. It also lists cumulative fixes available for WebSphere Commerce.

Recommended fixes and settings are fixes and settings that you should use if you want to optimize your environment. WebSphere Commerce and its related products regularly release fix packs and individual interim fixes for public download. Fix packs contain multiple corrections and improvements in the areas of function, security, stability, and performance. It is recommended that you run your WebSphere Commerce site with current fix pack levels. As with all production changes, the application of a fix pack or interim fix should be subject to rigorous functional and performance verification with your custom code.

Note: For more information about the minimum fixes for IBM WebSphere Commerce Version 7 releases that you require in order to receive support, see Required fixes for WebSphere Commerce Version 7.

Even if an update is not in your schedule, you should review the information about recommended fixes and settings in this topic, and the links it contains. You should also keep informed about the corrections and improvements included with each WebSphere Commerce fix pack. You can use this information to determine how your site might benefit from an upgrade. Likewise, you should review the links to the fix pack information for other products that are listed in this topic to determine how your site might benefit from upgrading them.

The information on this page should be reviewed in parallel with the information in the following sections:

Tips:

Subscribe to WebSphere Commerce notifications to keep up-to-date with support updates.
To find out about interim fixes that address security vulnerabilities, see Security bulletins.

IBM i-specific fixes are delivered by PTF. You should install the latest PTF of WebSphere Application Server, Java, IBM HTTP Server, and DB2. See the following URL for the latest PTF group information:

Preventive Service Planning - PSP

Recommended fixes and settings


Software	Recommended Level
WebSphere Commerce	The most current and recommended WebSphere Commerce fix pack is Fix Pack 9. The following cumulative interim fixes are the most current and are recommended: JR53048.fep JR52306.fep JR59483.fep JR53048.fp JR53048.fp JR52306.fp JR59483.fp If you are not on the latest Version 7 fix pack or feature pack level, review the following topics to see whether there are fixes you want to apply: APARs fixed in WebSphere Commerce fix packs APARs fixed in WebSphere Commerce feature packs Review the following topics for information about interim fixes that are not yet available in a fix pack, feature pack, or cumulative interim fix: List of additional fix pack APAR fixes List of additional feature pack APAR fixes Note: These interim fixes might not be required for your environment. Before you download or request any fixes, review the APAR descriptions to determine whether any of these fixes apply to you. As with all production changes, the application of a fix pack should be subject to rigorous functional and performance verification with your custom code. For the full list of available fix packs, see the Fix Pack for WebSphere Commerce Products . Note: WebSphere Commerce Version 7 for IBM i includes the fixes that are provided by Fix Pack 1. Therefore it does not need to be applied.
WebSphere Application Server	It is recommended that you use the latest version of WebSphere Application Server 7.0 available. For WebSphere Application Server 7.0.0.`x`, apply the fixes for CVE-2015-5015 and CVE-2015-2017 to correct security vulnerabilities. For WebSphere Application Server 7.0.0.37, apply interim fix IV69354 to correct a Java SDK performance regression. For WebSphere Application Server 7.0.0.0 through 7.0.0.035, apply interim fix PI27101 to upgrade to IBM SDK, Java Technology Edition, Version 6 Service Refresh 16 Fix Pack 2. WebSphere Application Server 7.0.0.33 upgrades Java to Java SDK 1.6 SR16, causing decryption errors with 32-hexadecimal character merchant keys. For more information about this issue, including instruction on how to resolve it, see Encryption errors after upgrading to Java 1.6 SR16. WebSphere Application Server 7.0.0.31 contains a fix for PM95795. This APAR addresses an issue with Asynchronous input/output (AIO) on the Windows platform, as explained in the technote Application server may stop responding to requests and hung threads may be seen on Windows with Asynchronous I/O enabled. In addition, review the information in WebSphere Application Server fixes for any applicable interim fixes for the WebSphere Application Server Fix Pack that you are using. To set up an agent that collects Java configuration and performance data, see Setting up IBM Health Center to collect performance data. Notes: When you install a WebSphere Application Server Fix Pack, all interim fixes are removed. If you upgrade your WebSphere Application Fix Pack, then you do not need to install the 7.0.0.3 custom installation package. Use the IBM Installation Manager to upgrade the WebSphere Application Server 7.0 Test Environment running inside the WebSphere Commerce Development environment. Although you can also use the Update Installer 7.0, which is available for download in the WebSphere Application Server Fix Pack download page, its use might prevent you from using the IBM Installation Manager to install Fix Packs in the future.
IBM DB2	It is recommended that you use the latest DB2 fix pack. There are issues that are related to database schema creation when you use DB2 V9.7 Fix Pack 5 or later. See: Database schema creation might fail on DB2 V9.7 Fix Pack 5 (or later) when you install or upgrade from a WebSphere Commerce version older than V7.0.0.6 With DB2 9.7, you must set the `DB2_ENABLE_THREAD_UNLOCK_EXTENDED` variable that is enabled by DB2 9.7 APAR#IC79285, or included in DB2 9.7 Fix Pack 6 or later.
Oracle Database	adds the ability to pass the dbURL parameter to Solr utilities to specify the fully qualified JDBC URL. JR44616 resolves a problem that causes SearchIndexSetup to fail if the Oracle schema name is too long.
IBM Sterling Order Management (integration)	provides fixes and enhancements to the WebSphere Commerce integration with Sterling Order Management solution.
IBM Rational Application Developer	It is recommended that you use Rational Application Developer version Rational Application Developer Version 8.0.4.2 iFix 1, or a higher Version 8.0 fix pack. For information about how to set up Rational Application Developer, see Installing Rational Application Developer or Rational Software Architect.