Configuring the JRE

This section describes the Java Runtime Environment (JRE), and how to configure it for the various supported platforms.

Due to the changes in Fix Pack D, the versions of the JREs included in TrueSight Middleware and Transaction Monitor have been updated. Refer to the table below for details.

Where a JRE is provided by TMTM for a particular platform it is included in the bootstrap and dependent components are configured to look for the JRE in a default location relative to their directory (based on the default agent layout).

Depending on the monitored technology, it might not always be appropriate to use the provided JRE. In these cases, set a JAVA_HOME environment variable for that particular monitoring extension so that it uses the appropriate JRE. If you want to define an alternative JRE for your platform, see Defining alternative JREs for Java extensions.

Where a JRE is not provided for the platform, one must be available for those components that require it. In those cases the JAVA_HOME environment variable must be set to indicate where a JRE can be found.

When setting JAVA_HOME in your environment, consider the monitoring environment as a whole. Your monitoring requirements might call for multiple Java versions to be available, or multiple JREs configured with different settings (e.g. for security configuration purposes).

Versions of JREs included in TMTM

PlatformVersion of agent JRE included in TMTM
Windows 32-bitRemoved (use 64-bit JRE)
Windows 64-bitJava 11
Linux x86 32-bitRemoved (use 64-bit JRE)
Linux x86 64-bitJava 11
AIX PPC64Java 8
Solaris SPARCJava 8 (deprecated, no further updates)
Solaris x86Java 8 (deprecated, no further updates)
HPUX IA64Java 8
zLinuxNo TMTM JRE supplied, user to provide Java 8 or later compatible JRE
z/OSNo TMTM JRE supplied, user to provide Java 8 or later compatible JRE
i5/OSNo TMTM JRE supplied, user to provide Java 8 or later compatible JRE
Was this page helpful? Yes No Submitting... Thank you