Publié Thu, 27 Sep 2018 16:18:38 GMT par Steve Shriver Application Specialist

A customer has a requirement to install any Java updates that are available. This has caused some problems with the full-text server (Version 7 - on premises). Is there any workaround for this or must we stick with the version of the Java SDK that comes with the installer media.

Thanks,

Publié Thu, 27 Sep 2018 18:32:04 GMT par Tim Ohm

I can't speak directly to DW7 & its specific versions of Tomcat and SOLR, but in the end it is still just a Tomcat instance.  Check out the Tomcat server properties - it could be the JVM is hard coded.  

From an elevated command prompt, navigate to the install directory of FT Server.  Run the configdwtomcat.cmd file - you'll be able to edit all the settings for the Tomcat server...RAM, JVM startup properties, etc - and the path to the JVM Tomcat will try to use.  Make sure that has the correct path for the SDK you just installed.  

https://www.docuware.com/sites/default/files/forums-images/FTServerProperties.PNG

Publié Thu, 27 Sep 2018 20:03:54 GMT par Phil Robson DocuWare Corporation Senior Director Client Services, Americas

I really do not think it matters too much these days if a Java Update is installed. Keep in mind that we distribute each version of DocuWare with a specific version of the JRE. Running Solr on a different version may lead to problems with Fulltext. So, regardless that updates have to be installed, if there is any mis-behavior from fulltext use Tim's guide above to reset Solr back to the JRE that was shipped with the version of DocuWare installed - OR - if it is running the released version then set it to the new one.
Recently I observed a 6.12 Solr running an updated JRE when I was troubleshooting other fulltext issues. So I set it back to the released version. In retrospect, it was not the root of the problem so I could have left it running the update. Not an exact science.

 

 

Phil Robson
Senior Director Support Americas

You must be signed in to post in this forum.