Managing Java installs
Automatically manage Java installs and upgrades from within configuration profiles. Manage installs of JCE Policy files.
Automatically manage Java installs and upgrades within configuration profiles. Managing Java installs is enabled by default in Lifecycle Manager, which downloads the JRE package and accepts the license on your behalf. The JRE or JDK is required for most DataStax products; including DataStax Enterprise (DSE), Lifecycle Manager (LCM), and OpsCenter. You can also point to your own internal download location for packages.
If there is no Java version found on a target during an install job or configuration job, LCM installs the specified version of Java. If a Java version is found but it does not match the specified version, LCM installs the specified version of Java specified alongside any outdated or incorrect version already installed. If managing Java is disabled, and no version of Java is found on the target, the install job fails.
java -version java version "1.8.0_60" Java(TM) SE Runtime Environment (build 1.8.0_60-b27) Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
In the above example, the 1.8.0
is the major version,
60
is the update version, and 27
is the build.
If your organization requires a version other than the default provided, enter the
version information in the java-setup page accessed in the Lifecycle
Manager section of the Config Profile pane. For
more details about Java version naming conventions, see the Oracle documentation.
Prerequisites
Procedure
- Click Config Profiles from the Lifecycle Manager navigation menu.
- Click the edit icon for the config profile you want to edit, or click Add config profile if you have not already created a profile.
-
In the Config Profile pane under the Lifecycle
Manager section, click Java Setup.
The settings including defaults for managing Java install versions appears. Click the information (i) icon to view information inline for each available field.
-
Make any changes to the available options in the Java
pane:
-
Make any changes to the available options in the JCE
Policy pane:
- Click Save.
What's next
- Configure a package proxy to cache and expedite package downloads.
- Run a configure job to apply the config profile changes.