If you aren't touching java on the server I doubt you'll notice any difference. What you have to watch out for on the client side is browser compatibility for plugins people might use. Nothing that is 'Remedy' related gets installed that way for a reason as far as I know.
When you upgrade on your servers there are all sorts of little ways to get caught by surprise that depend on how creative you got when java was first installed and whether your secondary tools installed their own copies of a JVM. If you've kept track of it all and kept your design clean, it is easy to upgrade on the server. If not... enjoy. 8) -al -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Lisa Singh Sent: Tuesday, June 18, 2013 1:04 AM To: [email protected] Subject: Really dumb question re Java. One of my bosses asked to ensure the rollout of Java 7.21 was "compatible" with Remedy. I personally can't think of any reason the Java VM would matter in the case of Remedy (with the exception of Analytics) - am I missing a portion of Remedy proper that uses *any* client-side Java? Surely the point of Tomcat is to do all the Java server side. Can anybody confirm? Kind Regards, Lisa _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
smime.p7s
Description: S/MIME cryptographic signature
