WebSphere Commerce Version 8.0.4.23 or later

Upgrading a WebSphere Commerce cluster to Java 8

In this task you will upgrade an existing WebSphere Commerce cluster 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 cluster 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 8.0.4.27 to Java 8, see Upgrading a WebSphere Commerce cluster 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 8.0.4.23 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 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.
    • For IBM i OS operating systemNew instance creation is not supported on IBM i.
  • Important: Ensure that the upgrade is completed without downtime by completing the following task in the correct order. Update your machine running deployment manager first before upgrading federated servers one by one.

Procedure

  1. Upgrade your existing WebSphere Application Server traditional to version 8.5.5.18 or greater.
    Note:
  2. On the deployment manager machine, navigate to the WASInstallDir/bin/ directory in a command prompt, and run the following commands:
    • LinuxAIX 
      managesdk.sh -setCommandDefault -sdkname 1.8_64
managesdk.sh -enableProfile -profileName dmgr -sdkName 1.8_64 -enableServers
    • Windows Windows
      managesdk.bat -setCommandDefault -sdkname 1.8_64
managesdk.bat -enableProfile -profileName dmgr -sdkName 1.8_64 -enableServers
  3. Start WebSphere Application Server deployment manager.
  4. For each server with federated nodes complete the following steps:
    1. Stop all WebSphere Commerce and WebSphere Commerce search servers from the WebSphere Application Server deployment manager.
    2. Stop the node or nodes.
    3. Upgrade your existing WebSphere Application Server traditional to version 8.5.5.15 or higher.
      Note:
    4. Upgrade your existing IBM SDK Java version to the same level, or greater. The associated level for WebSphere Application Server 8.5.5.15 is IBM SDK Java Technology Edition Version 8.0.5.27. To download and install IBM SDK Java Technology Edition Version 8.0.5.27, see Installing and uninstalling SDK Java Technology Edition Version 8.0 on distributed operating systems .
      Important: In the package group name window, select IBM WebSphere Application Server V8.5.
    5. Start the node or nodes.
    6. From WebSphere Application Server deployment manager, update the JAVA_Home WebSphere variable to point to the new Java location.
    7. Synchronize the node or nodes, and then stop the node or nodes.
    8. Navigate to the WASInstallDir/bin/ directory in a command prompt, and run the following command:
      • LinuxAIX 
        managesdk.sh -setCommandDefault -sdkname 1.8_64
      • Windows 
        managesdk.bat -setCommandDefault -sdkname 1.8_64
      For each node, run the command:
      • LinuxAIX 
        managesdk.sh -enableProfile -profileName node_name -sdkName 1.8_64 -enableServers
      • managesdk.bat -enableProfile -profileName node_name -sdkName 1.8_64 -enableServers

      Where node_name is the name of the node.

    9. Start the node or nodes, and then synchronize the node or nodes.
    10. Restart the server to pick up the new Software Development Kit configuration.
  5. Replace the references to Java within your environment.
    • WebSphere Commerce Version 8.0.4.24 or laterIf you are using WebSphere Commerce version 8.0.4.24 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 8.0.4.23.

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

      LinuxAIX
      • 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
      Windows
      • 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
  6. LinuxAIX Update the file permissions for the application by running the wcnonroot utility script.
    In a command prompt, run the utility:
    WC_installdir/bin/wcnonroot.sh

Results

Your WebSphere Commerce cluster environments are 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.