Installation · Lesson

Java

Quick answer

IdentityIQ requires a specific supported JDK version. Install it, set JAVA_HOME, and confirm the version before deploying.

Key takeaways

Prerequisites for Java
Step-by-step install path
Common pitfalls and fixes
Verification after install

IdentityIQ is a Java application, and it requires a specific supported JDK version for each release. Java version mismatch is one of the single most common causes of a failed or unstable installation, so getting the runtime right is a genuine prerequisite, not a detail.

Choosing the right JDK

Always consult the release notes / compatibility matrix for your exact IdentityIQ version and install the JDK version it lists as supported. Newer is not automatically better, running on an unsupported JDK can cause subtle failures, class incompatibilities, or refusal to start. Match the vendor guidance precisely.

Step by step

1. Install the supported JDK version on the server.
2. Set JAVA_HOME to the JDK location and add its bin to PATH for the service user.
3. Verify with java -version that the active runtime matches the supported version, including vendor and update level.
4. Configure JVM options (heap, GC) via the application server's environment script.
5. Proceed with Tomcat and IdentityIQ setup.

Common gotchas

Multiple JDKs installed: the shell/service may pick a different one than you expect; verify what JAVA_HOME actually points to for the service user, not just your login shell.
Service vs interactive environment: a systemd service or Windows service may not inherit your shell's JAVA_HOME; set it in the service configuration.
Vendor differences: use the JDK distribution your release supports.

Verify

The definitive check is that the running application server reports the supported Java version at startup and IdentityIQ loads cleanly. If startup fails, the logs almost always name a Java or class incompatibility first.

Common pitfalls

Unsupported JDK version for the release.
JAVA_HOME set for your login but not the service.
Ambiguous multi-JDK environments picking the wrong runtime.

Want to learn this properly?

Our live, instructor-led SailPoint Training covers this hands-on, with real projects and a certification path.

See the course Ask a question

Check your understanding

What are the prerequisites for Java?
- A. The application and app-server logs, which usually point to database, Java or permission issues.
- B. A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
- C. Confirm the app server starts, the schema is present, and login works.
Show answer
B. A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
How do you verify the install?
- A. The application and app-server logs, which usually point to database, Java or permission issues.
- B. Confirm the app server starts, the schema is present, and login works.
- C. A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
Show answer
B. Confirm the app server starts, the schema is present, and login works.
Confirm the app server starts, the schema is present, and login works.
Where do you look first on failure?
- A. The application and app-server logs, which usually point to database, Java or permission issues.
- B. Confirm the app server starts, the schema is present, and login works.
- C. A supported Java runtime, a reachable database, and the IdentityIQ files with correct permissions.
Show answer
A. The application and app-server logs, which usually point to database, Java or permission issues.
The application and app-server logs, which usually point to database, Java or permission issues.

Frequently asked questions

What does the term Java refer to in SailPoint?

What is worth checking first with Java?

If startup fails, the logs almost always name a Java or class incompatibility first.

What tends to go wrong with Java?

Unsupported JDK version for the release. JAVA_HOME set for your login but not the service. Ambiguous multi-JDK environments picking the wrong runtime.