A default JDK can be configured for sessions that do not explicitly set a JDK in their code editor settings. The JDK configuration is used for code completion and compiling scripts.
When you click on the [Configure JDKs] button, the JDK configuration dialog is shown.
If you do not define a default JDK, JProfiler will use the JRE that is used to run the JProfiler GUI. In that case, code completion does not offer parameter names in the JRE and there is no Javadoc for JRE classes.
Profiling sessions where the profiled JVM is launched by JProfiler need a JRE configuration. Here you can configure the default JRE for new sessions. It will be selected in the JRE drop-down list in the application settings after you create a new session.
When you click on the [Configure JREs] button, the JRE configuration dialog is shown.