Working with Multiple Java Runtime Environments

Have any of these scenarios happened to you?

  • I tried to open an attachment using AutoVue and I get a blank page.
  • I need to launch the Java Client, but the JRE required to run it is later than the version required to run my application.
  • My security team says that I have to upgrade to the latest secure release of the JRE, but that means it won’t be compatible with my other software.

Java Runtime Environment (JRE) releases are very common as they typically address security concerns as well as introduce new features and functionality. Unfortunately, not all systems are certified and operational with the latest JREs. To help address this issue Oracle released a feature with Java 7 update 40 called “Deployment Rule Set” that will allow installing the latest JRE while still allowing older JREs to run with applications that require them.

In a nutshell, Deployment Rule Sets allow having multiple JREs installed on one machine and a file with rules will specify which JRE to use for a given application. For instance, the rules may indicate that for Agile use JRE 1.7, for EBS use JRE 1.6 and for everything else use 1.8. The solution is fairly simple, but should be handled by a system administrator who can push out the configurations to multiple user computers.

What’s the solution?

Download Whitepaper (PDF)

Keith Rust | Key Contributor

Keith Rust is the Solutions Manager in the Innovation Management practice at Inspirage. Keith has over 15 years of functional and technical Agile PLM experience, specializing in Product Collaboration, Product Quality Management, and the Agile Integration Framework. Keith has helped over 125 companies with various aspects of Agile implementations in medical device, semiconductor, hi-tech, pharmaceutical, aerospace, automotive, solar and telecommunications industries. He is also a regular contributor to various Agile PLM user groups.