Switching to Java Development Kit 1.7

By default IBM® WebSphere® Application Server Network Deployment comes with Java™ Development Kit (JDK) 1.6. IBM InfoSphere® Information Server requires Java Development Kit 1.7. You can install Java Development Kit 1.7 and use the managesdk command to switch the version of Java Development Kit that is used by WebSphere Application Server Network Deployment.

Procedure

  1. On the services tier computer, install Java Development Kit 1.7 to the location of your choice.
  2. Set Java Development Kit 1.7 to be used by the InfoSphere Information Server profile:
    • If you have not yet created a profile for InfoSphere Information Server, you can set Java Development Kit 1.7 to be used as the default for all profiles (The ⇒ symbol indicates a line continuation):
      AIX® Linux® Solaris
      WAS_install_path/bin/managesdk.sh -setNewProfileDefault ⇒
      -sdkname 1.7_64
      WAS_install_path/bin/managesdk.sh -setCommandDefault ⇒
      -sdkname 1.7_64
      Windows
      WAS_install_path\bin\managesdk.bat -setNewProfileDefault ⇒
      -sdkname 1.7_64
      WAS_install_path\bin\managesdk.bat -setCommandDefault ⇒
      -sdkname 1.7_64
    • If you already created a profile for InfoSphere Information Server, run the following commands to enable the profile to use Java Development Kit 1.7 (The ⇒ symbol indicates a line continuation):
      AIX Linux Solaris
      WAS_install_path/bin/managesdk.sh -enableProfile -profileName ⇒
      profile_name -sdkname 1.7_64 -enableServers
      WAS_install_path/bin/managesdk.sh -setCommandDefault -sdkname ⇒
      1.7_64
      Windows
      WAS_install_path\bin\managesdk.bat -enableProfile -profileName ⇒
      profile_name -sdkname 1.7_64 -enableServers
      WAS_install_path\bin\managesdk.bat -setCommandDefault -sdkname ⇒
      1.7_64
      
  3. Verify that Java Development Kit 1.7 is now used by the profile:
    • You can check by logging into the WebSphere Application Server Administrative Console and selecting the following options: Application servers > server1 > Java SDKs
    • You can check by using the managesdk command (The ⇒ symbol indicates a line continuation):
      AIX Linux Solaris
      WAS_install_path/bin/managesdk.sh -listEnabledProfile ⇒
      -profileName profile_name
      Windows
      WAS_install_path\bin\managesdk.bat -listEnabledProfile ⇒
      -profileName profile_name

      Sample output from the command:

      CWSDK1004I: Profile profile_name:
      CWSDK1006I: PROFILE_COMMAND_SDK = 1.7_64
      CWSDK1008I: Node ssominenNode01 SDK name: 1.7_64
      CWSDK1009I: Server server1 SDK name: 1.7_64
      CWSDK1001I: Successfully performed the requested managesdk task.