Engine JRE Synchronization

The Engine’s JRE is always kept in synchronization, by default, with its Primary Director. For example, when the Engine is installed, it downloads a JRE from the Director with which it was configured. If the Engine is moved to another grid that has a different JRE, it synchronizes prior to login to that grid.

There might be certain cases in which you might not want the JRE to automatically synchronize. To disable this, add the line jre=local to the intranet.dat file. This prevents the installer from downloading and unpacking the JRE.

Note	If JRE updating is disabled, it is the responsibility of the user to make sure the JRE is properly deployed on the Engines.

If an Engine’s configuration uses a different Director URL than the actual name of the Director (such as one using the fully-qualified domain name and the other using a short name), the JRE is not updated when an Engine migrates. Also, if a primary Director is not available and an Engine uses a secondary Directory, the JRE is not updated.