• No replies
228 Posts

Pinned topic Defaulting to eClient viewerEngine properties file

‏2012-03-28T14:59:43Z |
In a deployed eClient (WinServer 2003, eClient there is a file in the eclient.war directory that has the inso engine defined. There is another file in the cmbViewer.jar file that does not have the inso, but has the OnDemand engine.

It seems that after the install/deploy, for one time it uses the one in the eclient.war file, and I am able to view a Word 2003 doc in the applet viewer. After that, it uses the one from the jar (I see in the java log that it is loading the OnDemand engine) and says there are no engines to use.

How do you get it to consistently use the properties file from the eclient.war?