Additional supported and tested software

Some fix packs introduce support for newer operating systems, database versions, or browser support. The following table shows the additional software tested in various fix packs.

Supported software Introduced in fix pack
DB2 version 9.7 fix pack 1 WebSphere Commerce Version 7.0.0.1
  • SolarisLinuxAIXWindowsFor new WebSphere Commerce version 7.0.0.1 installations, if you want to use DB2 version 9.7, it must be installed before WebSphere Commerce. WebSphere Commerce version 7.0.0.1 does not automatically install DB2 version 9.7.1. After you have installed DB2, proceed with AIXLinuxSolarisWindows.
  • The terms of the IBM Software License Agreement for WebSphere Commerce Version 7.0 were modified under the "Supporting Programs" section with the addition of DB2 version 9.7. To review and accept the modified license agreement, run the installation program for WebSphere Commerce Version 7.0 Feature Pack 1 or higher, and accept the modified license.
    To activate the copy of the DB2 Version 9.7 program that is provided with WebSphere Commerce V7.0, you must download and use one of the following eImages (or equivalent physical media):
    • IBM DB2 9.7, Enterprise Server Edition - Restricted Use - QuickStart Guide and Activation Multiplatform Multilingual (CZ381ML)
    • IBM DB2 9.7, Express Edition - Restricted Use - QuickStart Guide and Activation Multiplatform Multilingual (CZ382ML)
    Unlike the supplied DB2 version 9.5 images, the activation key is not included within the DB2 version 9.7 eImages
  • For existing WebSphere Commerce version 7.0.0.0 users, if you want to migrate from DB2 version 9.5 fix pack 4 to DB2 version 9.7 fix pack 1, install WebSphere Commerce version 7 fix pack 1 first. After completing the installation of the WebSphere Commerce fix pack, proceed with the steps in Migrating your database from DB2 V9.5 to DB2 V9.7.
  • For a remote DB2 version 9.7.1 configuration copy the DB2 bind file from your DB2 server to your DB2 client before creating a WebSphere Commerce instance. This is caused by a DB2 limitation. For additional details about this problem, see DB2 version 9.7 APAR IC62106.
    Copy db2_adminotm.bnd from the server to the client bnd directory. By default, the bnd file is in the following directory:
    • SolarisLinuxAIX$INSTHOME/sqllib/bnd
    • WindowsDB2_installdir\bnd
    Note:
    • Ensure that both the server and client are the same fix pack level when you copy the files.
  • The DB2 Version 9.7 registry variable DB2_COMPATIBILITY_VECTOR is not supported.
  • Deprecated featureWebSphere Commerce Payments is deprecated in WebSphere Commerce Version 7. You cannot use DB2 Version 9.7 with WebSphere Commerce Payments.
64-bit WebSphere Application Server

WebSphere Commerce Version 7.0.0.1To review the supported 64-bit versions of WebSphere Application Server see WebSphere Commerce Version 7 software requirements.

  • Deprecated featureWebSphere Commerce Payments is deprecated in WebSphere Commerce Version 7. You cannot use 64-bit versions of WebSphere Application Server with WebSphere Commerce Payments.
Oracle 11gR2 WebSphere Commerce Version 7.0.0.2
AIX Version 7.1 WebSphere Commerce Version 7.0.0.2
Windows 7 WebSphere Commerce Version 7.0.0.2
Windows 2008 R2 WebSphere Commerce Version 7.0.0.3
Red Hat Enterprise Linux (RHEL) 6.1 WebSphere Commerce Version 7.0.0.4
DB2 Enterprise Edition Version 10.1 WebSphere Commerce Version 7.0.0.7
  • DB2 Enterprise Edition Version 10.1 requires a minimum of WebSphere Commerce V7.0 Fix Pack 7 (7.0.0.7) with APAR JR47608 and UPDI version 7.0.0.7.1
DB2 Enterprise Edition Version 10.5 WebSphere Commerce Version 7.0.0.8
  • DB2 Enterprise Edition Version 10.5 requires a minimum of WebSphere Commerce V7.0 Fix Pack 8 (7.0.0.8)