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

  • Consider using the most recent fix pack for WebSphere Commerce. For upgrading WebSphere Commerce to Java 8, see Upgrading WebSphere Commerce (runtime) to WebSphere Application Server bundled 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 supported with WebSphere Commerce fix packs that require Java 8 until version If you need to create a new WebSphere Commerce instance, you must use WebSphere Commerce or greater. Alternatively, you can use an older Java 7 fix pack, such as, before upgrading to Java 8 and a more recent WebSphere Commerce fix pack.
    • For IBM i OS operating systemNew instance creation is not supported on IBM i.


  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. Repeat the second command for each profile that exists.
    • LinuxAIX
      managesdk.sh -setCommandDefault -sdkname 1.8_64
      managesdk.sh -enableProfile -profileName $WASProfileName -sdkName 1.8_64 -enableServers

      For example:

      managesdk.sh -enableProfile -profileName demo -sdkName 1.8_64 -enableServers
      managesdk.sh -enableProfile -profileName demo_solr -sdkName 1.8_64 -enableServers
    • Windows
      managesdk.bat -setCommandDefault -sdkname 1.8_64
      managesdk.bat -enableProfile -profileName $WASProfileName -sdkName 1.8_64 -enableServers
      For example:
      managesdk.bat -enableProfile -profileName demo -sdkName 1.8_64 -enableServers
      managesdk.bat -enableProfile -profileName demo_solr -sdkName 1.8_64 -enableServers

    Where WASProfileName is the name of the profile 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.
    • WebSphere Commerce Version or laterIf you are using WebSphere Commerce version or greater.
      1. Navigate to the following directory.
        • LinuxAIXWC_installdir/bin/
        • WindowsWC_installdir\bin\
      2. Run the updateJava8 utility script.
        • LinuxAIXupdateJava8.sh
        • WindowsupdateJava8.bat
    • If you are using WebSphere Commerce version

      Manually update the references from java_1.7_64 to java_1.8_64 in the following files:

      • WC_installdir/bin/setenv.sh
      • WC_installdir/bin/dbclean.sh
      • WC_installdir/bin/di-preprocess.sh
      • WC_installdir/bin/configServerEnv.sh
      • WC_installdir/bin/createVirtualHosts.sh
      • WC_installdir/bin/dataloadenv.sh
      • WC_installdir/bin/di-calculateprice.sh
      • WC_installdir/bin/di-parallel-process.sh
      • WC_installdir/bin/indexpropEnhance.sh
      • WC_installdir/bin/migrateListPrice.sh
      • WC_installdir/bin/migratePDC.sh
      • WC_installdir/bin/migrateSearchFacet.sh
      • WC_installdir/bin/seourlkeywordgen.sh
      • WC_installdir/bin/webFeedLoad.sh
      • WC_installdir/bin/di-buildindex.sh
      • WC_installdir/install/wc_default.properties
      • WC_installdir/wcbd/deploy/server/wcbd-setenv.bat.template
      • WC_installdir/wcbd/deploy/server/wcbd-setenv.template
      • WC_installdir/wcbd/wcbd-setenv.bat.template
      • WC_installdir/wcbd/wcbd-setenv.template
      • WC_installdir\bin\setenv.bat
      • WC_installdir\bin\dbclean.bat
      • WC_installdir\bin\di-preprocess.bat
      • WC_installdir\bin\configServerEnv.bat
      • WC_installdir\bin\createVirtualHosts.bat
      • WC_installdir\bin\dataloadenv.bat
      • WC_installdir\bin\di-calculateprice.bat
      • WC_installdir\bin\di-parallel-process.bat
      • WC_installdir\bin\indexpropEnhance.bat
      • WC_installdir\bin\migrateListPrice.bat
      • WC_installdir\bin\migratePDC.bat
      • WC_installdir\bin\migrateSearchFacet.bat
      • WC_installdir\bin\seourlkeywordgen.bat
      • WC_installdir\bin\webFeedLoad.bat
      • WC_installdir\bin\di-buildindex.bat
      • WC_installdir\install\wc_default.properties
      • WC_installdir\wcbd\deploy\server\wcbd-setenv.bat.template
      • WC_installdir\wcbd\deploy\server\wcbd-setenv.template
      • WC_installdir\wcbd\wcbd-setenv.bat.template
      • WC_installdir\wcbd\wcbd-setenv.template
  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.