Skip to main content

Configure Java for AIQ

  1. Update guidance
your 

ConfigurePATH Javaenvironment only accordingvariable to the AIQGraalVM bin directory. (where <version> represents the graalvm version, ex: 21.3.0)
Syntax: export PATH=/Library/Java/JavaVirtualMachines/graalvm-ce-java11-<version>/Contents/Home/bin:$PATH
Example: export PATH=/Library/Java/JavaVirtualMachines/graalvm-ce-java11-21.3.0/Contents/Home/bin:$PATH

Update your JAVA_HOME environment variable to resolve to the GraalVM installation directory (where <version> represents the graalvm version, ex: 21.3.0)
Syntax: export JAVA_HOME=/Library/Java/JavaVirtualMachines/graalvm-ce-java11-<version>/Contents/Home/
Example: export JAVA_HOME=/Library/Java/JavaVirtualMachines/graalvm-ce-java11-21.3.0/Contents/Home/Verify your install was successful.
Syntax: java -version
Sample Output:
openjdk version and"11.0.13" deployment2021-10-19
OpenJDK modelRuntime in use. Java requirements can differ across AIQ releases, operating systems, installers, and legacy integrations.

Before configuration

  • Confirm the AIQ version and the supported Java orEnvironment GraalVM runtime.CE 21.3.0 (build 11.0.13+7-jvmci-21.3-b05)

OpenJDK 64-Bit Server VM GraalVM CE 21.3.0 (build 11.0.13+7-jvmci-21.3-b05, mixed mode, sharing)Check operating

 system,

installation

Next path,step: serviceMacOS account,Required and environment variables.

Remove or isolate conflicting Java installations when they affect AIQ startup.Validate permissionsConfigurations for AIQ services, scripts, and Test Nodes.

Validation workflow

  1. Confirm the runtime version from the same account that starts AIQ.
  2. Restart AIQ services after approved configuration changes.
  3. Review startup logs for runtime, path, or permission errors.
  4. Run a Scenario Editor and Service Suite smoke test after Java changes.

Last updated: OctoberJuly 7,31, 20262024

If you have any feedback on this topic, please contact us at documentation@appvance.ai

Back to top