Required fixes for WebSphere Commerce Version 7
This topic provides a list of the minimum fixes for IBM WebSphere Commerce Version 7 releases that you require in order to receive support.
Required fixes
Required fixes can apply to WebSphere Commerce and all corequisite software
All of the required WebSphere Application Server APAR fixes are included in the WebSphere Application Server Customized Installation Package. If you do not install WebSphere Application Server using the DVDs or images that are provided by WebSphere Commerce, you must ensure that these fixes are installed.
WebSphere Application Server required fixes
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.
The following table includes the minimum version that is required for the corresponding WebSphere Commerce feature and/or fix pack.
Fix | Type | Comments |
---|---|---|
WebSphere Application Server Version 7.0 Fix Pack 3 |
Fix Pack | The minimum required level of WebSphere Application Server is 7.0.0.3, and this version is installed if you use the WebSphere Application Server DVD image that is packaged with WebSphere Commerce. |
WebSphere Application Server Version 7.0 Fix Pack 11 or higher |
Fix Pack | If you want to install WebSphere Commerce Version 7 Feature Pack 2 or higher, you are required to use WebSphere Application Server 7.0.0.11 or a higher level of WebSphere Application Server Version 7.0.0. After you upgrade, apply recommended fixes that are not included in 7.0.0.11. These fixes are listed in the WebSphere Application Server Version 7.0.0.11 fixes table in WebSphere Application Server fixes. |
WebSphere Application Server Version 7.0 Fix Pack 29 or higher |
Fix Pack | If you want to install WebSphere Commerce Version 7 Feature Pack 7 or higher, or WebSphere Commerce Version 7 Fix Pack 8 or higher, you are required to use WebSphere Application Server 7.0.0.29 or a higher level of WebSphere Application Server Version 7.0.0. After you upgrade, apply recommended fixes that are not included in 7.0.0.29. These fixes are listed in the WebSphere Application Server Version 7.0.0.29 fixes table in WebSphere Application Server fixes. |
WebSphere Application Server Version 7.0 Fix Pack 9 |
Fix Pack | The minimum required level of WebSphere Application Server is 7.0.0.9. Before you install WebSphere Commerce Version 7, download and install the WebSphere Application Server Version 7 Fix Pack 9 for IBM i platforms. |
PM63290 | APAR | Fixes issue where an ArrayIndexOutOfBoundsException occurs in DecimalFormat.parse in a concurrency situation. |
APAR | Addresses a possible OCCException error when you use the JDBC mediator applyChanges method. This interim fix is a replacement for PM24066. This fix is available in WebSphere Application Server 7.0.0.15 or higher. | |
APAR | Addresses the BasicIndexOutOfBoundsException that occurs when you install a WebSphere Commerce fix pack on an existing instance, when you use WebSphere Application Server 7.0.0.3. This fix is available in WebSphere Application Server 7.0.0.7 or higher. | |
PM52049 | APAR | Fixes javax.naming.directory.AttributeInUseException when you update the password, on a WebSphere Commerce configuration that uses an LDAP server, when you use WebSphere Application Server 7.0.0.19. This fix is available in WebSphere Application Server 7.0.0.21 or higher. |
PM51981 | APAR | Fixes an issue in which an RDN attribute is not returned on a get() call, on a WebSphere Commerce configuration that uses an LDAP server, when you use WebSphere Application Server 7.0.0.19 or 7.0.0.21. You can contact WebSphere Application Server Support to obtain this fix. |
IBM HTTP Server required fixes
Fix | Type | Comments |
---|---|---|
PK96410 | APAR | Addresses an issue where "proxy: error reading status line from remote server" is added to the error log intermittently. This fix is available in the IBM HTTP Server fix pack 7.0.0.9 or higher. |
PK98225 | APAR | Addresses an issue where some responses that could have been cached were not being cached, resulting in possible lower performance. This fix is available in the IBM HTTP Server fix pack 7.0.0.9 or higher. |
DB2 Database required fixes
Fix | Type | Comments |
---|---|---|
DB2 Database Version 9.5.0.4 | Fix Pack | The required version of DB2 Database is Version 9.5.0.4, and this version is installed if you use the DB2 DVD image that is provided by WebSphere Commerce. |
Lotus Connections required fix information
Fix | Type | Comments |
---|---|---|
LO43917 | APAR | These fixes are required for the Lotus Connections integration with Social Commerce to work. Obtain these fixes by registering forLotus Greenhouse. Then, accessing the following URL https://greenhouse.lotus.com/wikis/home?lang=en#/wiki/WebSphere%20Commerce%20Support/page/Welcome. |
LO43747 | APAR | |
LO44560 | APAR |
WebSphere Process Server/WebSphere Enterprise Service Bus required fix information
Fix | Type | Comments |
---|---|---|
IC77580 |
APAR | This fix is required if you are using Sterling Commerce. This fix prevents OutOfMemory errors when you create orders from Sterling Commerce. You can obtain the fix from IBM Fix Central. Make sure that you select the WebSphere Process Server product when you search for the fix. |