JREs

In the rare event that a particular service cannot use the default JRE that is deployed to the Engines, a JRE can be packaged as a Grid Library. The Service’s top-level Grid Library would then declare it as a dependency. When an Engine takes a Task, it then restarts using this JRE. Note that the JRE must be a supported version.

JREs are packaged as jre_name-version.gz or jre_name-version.zip where, jre_name includes jre-os. The version is the JRE version, for example, 1.8.0.331. The os is the platform, such as linux64, win64, linux, or win32.

For example, for linux 64: jre-linux64-1.8.0.331.tar.gz.

To package a JRE Grid Library, create a Grid Library that contains the JRE in a directory in the root of the Grid Library. Then, set the jre attribute in the grid-library element. For example, <grid-library ... jre="true" />

For a JRE Grid Library, you can optionally specify JVM arguments in the XML. To do so, add an <arguments> element to the root element. It can take any number of <property> elements, each containing a <name> element and an optional <value> element.

If the property has a value, the argument name=value is added. Otherwise, just the name argument is added.

If the same argument is set in the Engine Configuration and the Grid Library, the Grid Library overrides the Engine Configuration.

Note	Specifying the JVM debug port inside a Grid Library results in unpredictable behavior and is not supported. Set this functionality with the Debug Start Port setting on the Grid Components > Engines > Engine Configurations page.

For an example of how to package a JRE Grid Library, see the "Deploying Services" section of the TIBCO GridServer® Administration.