A Java Runtime Environment (JRE) must be installed on end-user machines for many ITNM UI features to work. The Oracle JRE 1.6 is End-Of-Life, and Oracle recommends upgrading to JRE 1.7. However, JRE 1.7 is not yet supported by ITNM 3.9 at this time.
What is the issue, and why is it relevant to customers?
A Java Runtime Environment (JRE) must be installed on end-user machines for many ITNM UI features (e.g. Network Views) to work. The Oracle JRE 1.6 is End-Of-Life [reference: 1] as of a final release in mid-June 2013 , and Oracle recommends upgrading to JRE 1.7 . However, JRE 1.7 is not yet supported by ITNM 3.9 at this time .
What does this mean for customers?
This means that Oracle no longer provides free support for JRE 1.6, neither is it committed to any future updates for JRE 1.6, even if issues with this JRE arise in the future.
What options does an ITNM 3.9 customer have?
Continue to use Oracle JRE 1.6 until JRE 1.7 formally supported by ITNM.
IBM will target support of Oracle & IBM flavours of JRE 1.7 in ITNM 3.9 FP4 . Please note that this is a roadmap target and is subject to change without notice; it does not represent a formal commitment by IBM.
Use the IBM JRE 1.6, which is still in support.
The End-of-Service date for IBM JRE 1.6, when IBM will stop making fixes generally available (equivalent to Oracle's EOL), is September 2017 for all non-z/OS platforms .
Why can't a customer simply upgrade to Oracle or IBM JRE 1.7?
Basic verification testing of ITNM 3.9 against both Oracle and IBM flavours JRE 1.7 has demonstrated known issues with JRE 1.7. Early versions of JRE 1.7 had security issues unique to that JRE level . The current version (Oracle JRE 184.108.40.206, and IBM equivalent) has a significant logging issue which prevents ITNM components from operating on any end-user machine with this version of JRE 1.7 installed . A fix for this bug is targeted for inclusion in the next Oracle JRE release (220.127.116.11), and in the IBM equivalent.