WebSphere Commerce Version 8.0.4.27 or later

Upgrading to WebSphere Commerce 8.0.4.27 or greater

There are environment prerequisites to upgrade WebSphere Commerce to versions 8.0.4.27 or greater.

Important: To upgrade to WebSphere Commerce or WebSphere Commerce Developer 8.0.4.30 from any previous version, you must first upgrade to 8.0.4.29. This is required due to changes to JAR files that were made due to security vulnerabilities.

Warning:

WebSphere Commerce instance creation is not supported with WebSphere Commerce fix packs that require Java 8 until version 8.0.4.30. If you need to create a new WebSphere Commerce instance, you must use WebSphere Commerce 8.0.4.30 or greater. Alternatively, you can use an older Java 7 fix pack, such as 8.0.4.25, before upgrading to Java 8 and a more recent WebSphere Commerce fix pack.
New instance creation is not supported on IBM i.

Before you begin

Ensure that you are using the correct version of WebSphere Application Server for the version of WebSphere Commerce that you are installing on your environments.
For more information, see:
- Recommended software, fixes, and settings for WebSphere Commerce Version 8.0
- Installing and preparing WebSphere Application Server
  Important: WebSphere Application Server 8.5.5.22 or greater will not install if Java 7 is in use. To install WebSphere Application Server 8.5.5.22 or greater, you must first uninstall Java 7 before upgrading. For more information, see the WebSphere Application Server V8.5.5.22 release topic in the WebSphere Application Server documentation.

Procedure

Upgrade your WebSphere Commerce production environments:

Install WebSphere Commerce 8.0.4.27 or greater.
Upgrade your runtime environments to use WebSphere Application Server bundled Java 8 (1.8_64_bundled).
See Upgrading WebSphere Commerce 8.0.4.27+ to Java 8.
Note:
- If you have previously upgraded your environments to bundled Java 8, you can skip this step.
- If you have previously upgraded your environments to a standalone version of Java 8 (1.8_64), you must again update your environment to use the version of the Java SDK that is bundled with WebSphere Application Server.
- You can observe the version of Java 8 that you are using by using the following commands:
  1. In a command prompt, navigate to the WAS_installdir/bin/ directory.
  2. Run the following command:
    
    ./managesdk.sh -getNewProfileDefault
    
    managesdk.bat -getNewProfileDefault
    
    managesdk -getNewProfileDefault
    
    managesdk -getCommandDefault
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.
For more information on this required change, see Service refresh 7 in the IBM SDK, Java Technology Edition documentation.

Results

You have successfully upgraded your production environments to a later WebSphere Commerce Version 8 fix pack.

This upgrade included:

Upgrading your production environments to a later WebSphere Commerce fix pack level.
Ensuring that your production environments are using a supported version of Java 8, with the bundled WebSphere Application Server Java SDK.