IBM Support

How to manage different JAVA versions for different SDC or Transformer deployments

How To


Summary

How to manage different JAVA versions for different SDC or Transformer deployments

Objective

In this article, we will give some advice on how to manage different Java versions for different SDC or Transformer deployments on the same server. We will provide a “manual” solution and provide a couple of alternatives using other tools for this.

Steps

A very useful practice is to create “aliases” in our bash file for each Java version we have installed to avoid having to export each time the JAVA_HOME variable.

We create several aliases like the ones below:

alias j8='export JAVA_HOME=$(/usr/libexec/java_home -v 1.8.0_292);java -version'

alias j11='export JAVA_HOME=$(/usr/libexec/java_home -v 11.0.9i);java -version'

alias j="echo $JAVA_HOME;java -version"

Results

For instance, imagine we have an SDC 5.2 running in Java 8, but we want to deploy a new SDC 5.9.1 that will run in Java 11.

Open the terminal and execute the alias “j11” and then, deploy the SDC. It will recognize the Java version as 11 and will execute the SDC with the specific configuration of Java 11.

Alternatively, you can use other tools like jEnv or SDKMan to manage these commands more smoothly. Check the links below.

Additional Information

Document Location

Worldwide

[{"Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSM7CU","label":"IBM StreamSets Data Collector"},"ARM Category":[{"code":"","label":""}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"},{"Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSZUHT0","label":"IBM StreamSets Transformer for Spark"},"ARM Category":[{"code":"","label":""}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]

Document Information

Modified date:
16 March 2025

UID

ibm17186366