Install > Installing WebSphere Commerce > Prepare to install WebSphere Commerce


Required and recommended fixes for WebSphere Commerce v7


Required and recommended fixes

See: Recommended fixes and settings for WebSphere Commerce

Subscribe to WebSphere Commerce notifications to keep up-to-date with support updates.


Required fixes

WebSphere Commerce required fix information

Fix Type Comments
IZ63790 APAR Customers using a WebSphere Commerce server on Linux, and using an Oracle database need to install this fix.



WAS required fixes

Fix Type Comments
WAS v7.0 Fix Pack 3 Fix Pack The required level of WAS is 7.0.0.3, and this vis installed if you use the WAS DVD image packaged with WebSphere Commerce.

IBM recommends upgrading WAS to v7.0.0.9.

After upgrading, apply recommended fixes that are not included in 7.0.0.9. These fixes are listed in the section, Recommended additional fixes WAS v7.0.0.9 is installed

WAS v7.0 Fix Pack 9

Fix Pack The required level of WAS is 7.0.0.9. Before installing WebSphere Commerce v7, download and install the WAS v7 Fix Pack 9 for IBM i platforms.

All required WAS APAR fixes are included in the WAS Customized Installation Package. If you do not install WAS using the DVDs or images provided by WebSphere Commerce, ensure these fixes are installed.



IBM HTTP Server required fixes

Fix Type Comments
PK96410 APAR Addresses an issue where "proxy: error reading status line from remote server" appears in the error log intermittently
PK98225 APAR Addresses an issue where some responses that could have been cached were not being cached, resulting in possible lower performance.



DB2 Database required fixes

Fix Type Comments
DB2 Database v9.5.4 Fix Pack The required vof DB2 Database is v9.5.4, and this version is installed if you use the DB2 DVD image provided by WebSphere Commerce.



Lotus Connections required fix information

Fix Type Comments
LO43917 APAR Required for the Lotus Connections integration with Social Commerce.
LO43747
LO44560 		APAR Obtain from Lotus Greenhouse


Recommended fixes


WebSphere Commerce

IBM recommends upgrading to the latest available fix pack, WebSphere Commerce Fix Pack 1.

WebSphere Commerce v7 for IBM i includes the fixes provided by fix pack 1. Therefore it does not need to be applied.


WebSphere Application Server

IBM recommends upgrading WAS to v7.0.0.9. After upgrading, apply recommended fixes that are not included in 7.0.0.9. These fixes are listed in the section, Recommended additional fixes WAS v7.0.0.9 is installed

All required APAR fixes are included in the WAS Customized Installation Package. If you do not install WAS using the DVDs or images provided by WebSphere Commerce, ensure these fixes are installed.

When you install WAS Fix Pack 9, all iFixes are removed. If we will upgrade to Fix Pack 9; then you do not need to install the customized installation package.

WAS vFix Pack 9 is recommended for both WebSphere Commerce v7 and WebSphere Commerce v7.0.0.1. If you use WebSphere Commerce v7.0.0.0; then apply a APAR# JR36472 after upgrading to WAS vFix Pack 9. Contact WebSphere Commerce support to obtain this APAR.

The following table lists recommended APAR fixes that you can apply in addition to the required fixes.


WAS recommended fixes

Included in WAS Fix Pack Version Fix Comments
7.0.0.7 PK90588 Addresses the BasicIndexOutOfBoundsException that occurs when installing a WebSphere Commerce fix pack on an existing instance.
7.0.0.7 PK93269 Addresses an issue where Web Services application deployment experiences performance degradation.
7.0.0.7 PK99815 Addresses an issue with slow application deployment resulting from zip file decompression overhead.

Recommended for 32-bit WAS, but is already included with 64-bit WAS.

7.0.0.9 PK88962 Addresses an issue where a NoClassDefFoundError warning is received during an application update.
7.0.0.9 PK96229 Addresses an issue where in some certain conditions, some sensitive information might be logged in ffdc data.
7.0.0.9 PK96996 Addresses an issue where the systemapps.xml entries are not migrated when migrating WAS v6.1 to v7.0.
7.0.0.9 PK98225 Addresses an issue where some responses that could have been cached were not being cached, resulting in possible lower performance.
7.0.0.9 PK98999 Addresses an issue where the Application Profile service is not closing EAR file resources.

Recommended for 32-bit WAS. Already included with 64-bit WAS.

7.0.0.9 PM01912 Addresses an issue starting and stopping WAS due to an exception related to needing elevated privileges.
7.0.0.9 PK93927 Addresses an issue where batch EJBDeploy doesn't recognize the option 'nowarn' in WAS 7.0.0.5.
7.0.0.9 PK96928 Addresses an issue where a singleton attribute causes a sync failure between V7 DMGR and V5.1 nodes.
7.0.0.9 PM06623 Addresses an issue where applications which have been updated to use Java™ EE5 features have slow deployment and startup times.
7.0.0.9 PM07309 Addresses an issue where excess memory utilization is caused by redundant loads of application metadata.
7.0.0.9 PM12460 Addresses an issue where extra memory utilization is seen when annotations are used in relation to an Array type.

Recommended additional fixes if WAS v7.0.0.3, v7.0.0.5 or v7.0.0.7 is installed

Targeted for 7.0.0.11 PM08344 Addresses an issue where the WriteMethod of an extended bean class is not being introspected.

Recommended additional fixes if WAS v7.0.0.9 is installed

Targeted for 7.0.0.11 PM09810 Addresses an issue where WASPostUpgrade fails when migrating from WAS v5.1 to v7.0 on IBM i.
Targeted for 7.0.0.11 PM09935 Addresses an issue with high CPU usage with dynacache disk offload.
Targeted for 7.0.0.11 PK98471 Addresses an issue where migration to WAS 7.0 fails if migrating from a pre-6.1 system.
Targeted for 7.0.0.13 PM11768 Addresses an issue where an EAR file is removed from installedApps when a sync is issued between V7 DMGR and V5.1 nodes.


+

Search Tips   |   Advanced Search