Java Version - Perils of upgrading

Hi Iain,

The JRE supplied with Uniface is there primarily to provide an out-of-the-box experience. If preferred, an advanced installation can be configured to use an existing Java installation instead.

Java is used by Uniface for Tomcat/WRD, XSLT transformations, and Java Call-In functionality. The supported and verified Java versions are listed in the PAM, so I'd recommend aligning any upgrade with the versions documented there.

The Uniface updater does not update the JRE or Tomcat. This is intentional, as customers may have applied their own updates or configuration changes. As a result, applying a Uniface patch will not overwrite a newer Java version that you have installed.

As always, we recommend testing any Java upgrade in a non-production environment before rolling it out more widely.

Regards,
Mike

Hi Iain
Our customers did aks the same question.
Our answer was: “Use what you want, Java is only for Tomcat/WRD and UnifAce can handle anything you throw at it”
Never heard any complain :-)
But I don't want to rule out the possibility that certain combinations might cause problems. So, as Michael says, check the PAM.

Ingo

So, I just attempted to update one of my installs to use the latest Tomcat 11 instead of the installed one. This failed utterly. 
I compared the files in conf, and service.bat and tried to make intelligent choices what to keep from the new install and what to keep from the previous one. I obviously got something wrong because the service would not start with the terribly informative error “unknown function”. 

Does anyone have a step by step guide in what to keep and what to replace in the conf files and service.bat to get this to work? 

Regards, 

Iain