1. Which OpsRamp application or service requires Java?
The vProbe application, a core component of the Classic Gateway, requires Java. vProbe is responsible for discovery and monitoring operations.
2. Is Java still required for the Classic Gateway to function?
Yes. Java is required for the vProbe application to run in the Classic Gateway. You must have Java available on your host system. Java is bundled with the gateway installation.
3. Which Java version does the Classic Gateway depend on?
- Gateway version 21.0.0 and later: Uses Java 17 by default
- Gateway versions earlier than 21.0.0: Used Java 11 by default
To maintain backward compatibility, both Java 11 and Java 17 are supported in recent releases.
4. Can the Classic Gateway run on a lower Java version?
Yes, with conditions.
- You can use Java 11 as a fallback for supported gateway versions up to 21.x
- Use this fallback only for compatibility or issue-resolution scenarios (for example, if you experience discovery or monitoring issues with Java 17)
Minimum supported version (current):
- Java 11 (only for supported older gateway versions)
Important: Starting with Gateway version 22.0.0, Java 11 will no longer be supported, and Java 17 is mandatory.
5. Can Java be removed from the Classic Gateway server?
No. You cannot remove Java because the vProbe application depends on it.
You should:
- Use only the Java runtime bundled with the Classic Gateway
- Avoid manually upgrading, downgrading, or replacing the bundled Java version
Additional recommendations for Classic Gateway
- Always use the bundled Java runtime to ensure compatibility and supportability.
- Do not make manual Java version changes, as they may result in unsupported configurations.
- If you are still using Java 11, plan your migration to Java 17 before upgrading to Gateway version 22.0.0.