Switching vProbe Java Version on Classic Gateway Version 20.0.0

To switch the Java version used by gateway between Java 11 and Java 17 on a Classic Gateway (version 20.0.0), follow the steps below.
Before you begin,

  • Ensure that the gateway version is 20.0.0 before proceeding.
  • Run all commands as a user with the necessary administrative privileges (typically root user).
  • It is recommended to take a backup or snapshot of the environment before making changes.

To migrate vProbe from Java 11 to Java 17, run the following command:

sh /home/admin/bin/vprobe-migrate.sh 17

To revert vProbe from Java 17 to Java 11 (if needed), run the following command:

sh /home/admin/bin/vprobe-migrate.sh 11

Post Migration Validation

  1. Verify the Java Version in Use by vProbe Run the following command to confirm the vProbe service is using the correct Java version:
    systemctl status vprobe | grep java-1

You should see an output similar to the following (truncated for clarity):

/usr/lib/jvm/java-1.17.0-openjdk-amd64

Ensure the Java path reflects version 1.17.0 as shown above.

  1. Verify Gateway Tunnel Connectivity and Monitoring
    1. Confirm the gateway tunnel is active.
    2. Ensure that monitoring is functioning correctly for all resources connected to the gateway.