Sometimes you need to replace or update the default JDK that is provided with IBM® BigInsights™. For example, you might need to change the default JDK to:

  • Add security patches
  • Overcome performance related issues
  • Install some intermediate fixes based on clients’ request

This post describes how to replace the default JDK for a BigInsights installation. This process was tested in IBM BIgInsights version 2.0 to replace the default JDK from IBM JDK6SR11 to IBM JDK6SR12 on a five-node cluster. The steps below assume that the new JDK is ibm-java-sdk-6.0-12.0-linux-x86_64.tgz (IBM JDK 6SR12); change the name based on the version of the JDK that you are about to install.

Step 1: Upload

  • Upload the new IBM JDK to all of the destination computers in the $BIGINSIGHTS_HOME directory

Step 2: Run the following commands on each of the BigInsights cluster members (Data and  Management nodes):

  • cd $BIGINSIGHTS_HOME
  • sudo chmod 777 ibm-java-sdk-6.0-12.0-linux-x86_64.tgz
  • sudo chown biadmin:biadmin ibm-java-sdk-6.0-12.0-linux-x86_64.tgz
  • mv jdk/ jdk_orig
  • tar zxvf ibm-java-sdk-6.0-12.0-linux-x86_64.tgz
  • mv ibm-java-x86_64-60 jdk

Step 3: Run these commands on the console node:

  • cd $BIGINSIGHTS_HOME/hdm/artifacts
  • mv ibm-java-sdk-6.0-11.0-linux-x86_64.tgz ibm-java-sdk-6.0-11.0-linux-x86_64.tgz_orig
  • cp /home/bi/opt/ibm/biginsights/ibm-java-sdk-6.0-12.0-linux-x86_64.tgz ibm-java-sdk-6.0-11.0-linux-x86_64.tgz
  • cd $BIGINSIGHTS_HOME/hdm/todeploy
  • mv jdk.tar.gz jdk.tar.gz_orig
  • mv jdk.tar.gz.cksum jdk.tar.gz.cksum_orig
  • syncconf.sh (it will fail, it's OK)
  • cp jdk.tar.gz.cksum $BIGINSIGHTS_HOME/jdk/.deploy.cksum

for each node:

    • sftp root@nodename
    • put cp jdk.tar.gz.cksum

 

    • ssh root@nodename
    • chown biadmin:biadmin jdk.tar.gz.cksum
    • cp jdk.tar.gz.cksum .deploy.cksum
    • cp .deploy.cksum /home/bi/opt/ibm/biginsights/jdk/

Run syncconf.sh on console node (this time should work)

If the syncconf.sh command is successful, you have successfully installed and distributed the new JDK.

Step 4: Verification for each node:

  • ssh root@nodename
  • su - biadmin
  • java -version

Expected output for correctly installed IBM JDK6 SR12:

Image and video hosting by TinyPic

George Lapis (lapis@us.ibm.com) and Richard Ding (sding@us.ibm.com) also assisted with this post.

Join The Discussion

Your email address will not be published. Required fields are marked *