WebSphere Commerce Version or later

Upgrading WebSphere Commerce (runtime) to Java 8

In this task you will upgrade an existing WebSphere Commerce stand-alone runtime environment to use Java 8. Upgrading to a newer version of Java and WebSphere Application Server will allow you to ensure compatibility and continue receiving product support. The specific version of Java that is run on your runtime will be IBM SDK Java Technology Edition Version 8.0 for WebSphere Application Server.

Before you begin

  • Ensure that you are planning on upgrading to the latest WebSphere Commerce fix pack. If you are using an older version of WebSphere Commerce, see the previous version of this topic Upgrading WebSphere Commerce (runtime) to Java 8.
  • You can only update to use IBM SDK Java Technology Edition Version 8 if your existing WebSphere Commerce runtime instance is on WebSphere Commerce or greater. For information about installing fix packs, see Installing maintenance for WebSphere Commerce.
    Note: If you have already upgraded your environment to Java 8 before installing this fix pack, you must update the references to Java in your utilities after applying the fix pack (Step 6).
  • 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.


  1. Upgrade your existing WebSphere Application Server to version or greater.
  2. Stop all WebSphere Commerce servers.
  3. 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.
    • LinuxAIX
      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
    • Windows
      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.
    • LinuxAIX
      managesdk.sh -listEnabledProfileAll
    • Windows
      managesdk.bat -listEnabledProfileAll
  4. Replace the references to Java within your environment.
    1. Navigate to the following directory.
      • LinuxAIXWC_installdir/bin/
      • WindowsWC_installdir\bin\
    2. Run the updateJava8 utility script.
      • LinuxAIXupdateJava8.sh
      • WindowsupdateJava8.bat
  5. LinuxAIX Update the file permissions for the application by running the wcnonroot utility script.
    In a command prompt, run the utility:


Your WebSphere Commerce runtime environment is upgraded to use Java 1.8 on a newer version of WebSphere Application Server. This version of Java and WebSphere Application Server ensures continued product support.