Co-requisite software requirements for WebSphere Commerce

Ensure that the co-requisite software that is used for your WebSphere Commerce installation meets the levels listed in this topic.

For this information, and for more on the required software levels of both integration and WebSphere Commerce Developer co-requisite software, see Recommended software, fixes, and settings for WebSphere Commerce Version 8.0.

WebSphere Application Server

  • The levels of WebSphere Application Server that are tested and verified by HCL for each release are:
    • WebSphere Commerce Version 8.0.4.30Version 8.5.5 Fix Pack 24 (or 8.5.5.24)
    • WebSphere Commerce Version 8.0.4.29Version 8.5.5 Fix Pack 21 (or 8.5.5.21)
    • WebSphere Commerce Version 8.0.4.28Version 8.5.5 Fix Pack 20 (or 8.5.5.20) + PH42728
    • WebSphere Commerce Version 8.0.4.27Version 8.5.5 Fix Pack 19 (or 8.5.5.19)
    • WebSphere Commerce Version 8.0.4.26Version 8.5.5 Fix Pack 18 (or 8.5.5.18)
    • WebSphere Commerce Version 8.0.4.25Version 8.5.5 Fix Pack 17 (or 8.5.5.17)
    • WebSphere Commerce Version 8.0.4.24Version 8.5.5 Fix Pack 15 (or 8.5.5.15)
    • WebSphere Commerce Version 8.0.4.23Version 8.5.5 Fix Pack 15 (or 8.5.5.15)

    For use with Java 8, the minimum required level of WebSphere Application Server is 8.5.5 Fix pack 15 (or 8.5.5.15).

    It is recommended that you install the latest fix pack for WebSphere Application Server Version 8.5.5.
    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.
  • In addition, review the information in Fixes for corequisite supported software 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.

Database

IBM SDK Java Technology

  • WebSphere Commerce requires a 64-bit version of SDK Java Technology Edition.
    Important: Beginning with 8.0.4.26, WebSphere Commerce only supports IBM Java Technology Edition Version 8.0. This is included bundled with your WebSphere Application Server installation.

    If you plan to upgrade to WebSphere Commerce 8.0.4.26 or greater, or any subsequent fix pack, you must upgrade WebSphere Commerce to Java 8. For more information, see Upgrading WebSphere Commerce 8.0.4.27+ to Java 8.

  • The following versions highlight the recommended versions of IBM SDK Java Technology Edition for use with WebSphere Commerce.