A typical Silk Performer installation includes a Java Runtime Environment. The JRE is required for several components and processes, for example for the installation itself and for Java Explorer. It is also in the search path for projects that require a JRE. With Silk Performer 19.5 the JRE from Oracle has been replaced by the Zulu JRE from Azul Systems. Zulu builds are based on OpenJDK and they are certified for Java SE TCK compliance on x64 reference architecture systems.
You can also use your own Oracle JRE or JDK by configuring the Java profile settings accordingly.
A Java Runtime Environment is required for several script types, such as Oracle Forms, Silk4J, AMF, and of course Java Framework. By default, the JRE configured in the profile settings is used. However, if the configured location turns out to be wrong, Silk Performer automatically attempts to find an alternative by scanning the Windows registry or by using the JRE that is installed by the Silk Performer installer in the home/JRE directory. This smart JRE search functionality is also applied on remote agents.
JUnit tests are now executed using a JUnit runner rather than by direct method calls. This allows you to make use of annotations in the Java code to parameterize your tests.
JVM options are now passed on to Silk4J, so that you can further parameterize your Java test environment.