If you are upgrading from WebSphere Commerce 8.0.4.26 or below, to WebSphere Commerce 8.0.4.27 or greater, you must ensure that your environments are
upgraded to support it.
Warning: WebSphere Commerce instance creation is not
currently supported with available WebSphere Commerce fix packs that require
Java 8. If you need to create a new WebSphere Commerce instance, you must do so
with Java 7, before upgrading to Java 8.
Procedure
Upgrade your development environments.
-
Install WebSphere Commerce Developer 8.0.4.27 or greater.
-
Upgrade your development environments to Java 8.
- If you have not upgrade your environment to Java 8 previously,
upgrade your
development environments to Java 8.
- If you have previously upgraded your environments to Java 8, you
must again update your environment to use the version of the
Java SDK that is bundled with WebSphere Application Server.
- Stop the WebSphere Commerce Test Server.
- Obtain the WebSphere Application Server Profile name. Open the
WCDEInstallDir\wasprofile\logs\AboutThisProfile.txt
text file and locate the name. For example,
WCDE_E~1_145207
.
- In a command prompt, run the following commands:
- Set the command default to use the bundled
Java version 8.0
SDK.
WASInstallDir\bin\managesdk.bat -setCommandDefault -sdkname 1.8_64_bundled
- Set any newly created profiles to default to
use the bundled Java version 8.0
SDK.
WASInstallDir\bin\managesdk.bat -setNewProfileDefault -sdkname 1.8_64_bundled
- Set your existing profile to use the bundled Java version 8.0
SDK.
WASInstallDir\bin\managesdk.bat -enableProfile -profileName profileName -sdkName 1.8_64_bundled
Where
profileName is the profile name from
the previous step.
For
example:
W:\WebSphere\AppServer\bin\managesdk.bat -enableProfile -profileName WCDE_E~1_145207 -sdkName 1.8_64_bundled
-
Upgrade your WebSphere Commerce production environments.
-
Install WebSphere Commerce 8.0.4.27 or greater.
-
Upgrade your production environments to Java 8.
- If you have not upgrade your environment to Java 8 previously,
Upgrade
your runtime or cluster environments to Java 8.
- If you have previously upgraded your environments to Java 8, you
must again update your environment to use the version of the
Java SDK that is bundled with WebSphere Application Server.
Navigate to the
WASInstallDir/bin/ directory
and run the following commands to set the command default, set newly created
profiles, and set existing profiles, to use the WebSphere Application Server
bundled version of the Java 8 SDK. Repeat the existing profile command for
each profile that exists.

managesdk.sh -setCommandDefault -sdkname 1.8_64_bundled
managesdk.sh -setNewProfileDefault -sdkname 1.8_64_bundled
managesdk.sh -enableProfile -profileName WASProfileName -sdkName 1.8_64_bundled -enableServers
For example:
managesdk.sh -enableProfile -profileName demo -sdkName 1.8_64_bundled -enableServers
managesdk.sh -setNewProfileDefault -sdkname 1.8_64_bundled
managesdk.sh -enableProfile -profileName demo_solr -sdkName 1.8_64_bundled -enableServers
managesdk.bat -setCommandDefault -sdkname 1.8_64_bundled
managesdk.bat -setNewProfileDefault -sdkname 1.8_64_bundled
managesdk.bat -enableProfile -profileName WASProfileName -sdkName 1.8_64_bundled -enableServers
For
example:
managesdk.bat -enableProfile -profileName demo -sdkName 1.8_64_bundled -enableServers
managesdk.bat -setNewProfileDefault -sdkname 1.8_64_bundled
managesdk.bat -enableProfile -profileName demo_solr -sdkName 1.8_64_bundled -enableServers
Where
WASProfileName is the name of the profile
that you are modifying.
Note: You can use the
managesdk utility script to enumerate the
profiles, and verify their Java version.
-
If you have, or are upgrading to a Service refresh 7 version
of Java 8, such as WebSphere Application Server version 8.5.5.21 with Java
version 8.0.7.0, you must revert to the previous JCE security
provider.
Using the
com.ibm.crypto.provider.IBMJCEPlus
security
provider causes a memory leak, leading to performance implications.
- Open the jre/lib/security/java.security
configuration file for editing in your SDK installation directory.
- 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
- 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 environments to the
latest WebSphere Commerce Version 8 fix pack.This upgrade included:
- Upgrading your environments to the latest WebSphere Commerce fix pack
level.
- Ensuring that your WebSphere Commerce development environment is using Rational Application Developer 9.6.
- Ensuring that your environments are using a supported version of Java 8, with
the bundled WebSphere Application Server Java SDK.
- Ensuring that the default WebSphere Application Server JCE security provider remains
IBMJCE
.