2.4.0 Migration Guide
This guide helps detail what you'll need to do and what has changed. Much of this guide only applies if you have made custom modifications to WebViewer Server.
The Changes
WebViewer Server is now composed of 4 files,
embedded-server.jar,shared.jar,blackbox.war,demo.warApache Tomcat is now used as embedded software and configuration is now declared in code. Before we merged our binaries with an Apache Tomcat install.
To make configuration modifications now, one will need to modify various JAVA_OPTS on their system or in the container.
By default, WebViewer Server expects the contents of the
libsfolder 1 level above its working directory. This contains all binaries used in WebViewer Server's operation. This can be configured via TRN\_BIN\_DIRInside of the Docker Container
The root directory is now
/home/tomcat/wv-serverThe binary libraries are placed in
/home/tomcat/libs
Using the WebViewer Server Windows installer
Program execution now occurs in C:/ProgramData/Apryse
Logging Modifications
Internally we use log4j2 to manage our logging, and some customers may use a custom logging file for their setup. In 2.4.0 the way to overwrite this file is to now add this to your JAVA_OPTS:
Dlog4j.configurationFile=/path/to/log4j2.xml
This document will be updated if there are any more possible migration suggestions, feel free to submit any issues the new release might create for you via support.
**XRef Modifications
**If you are using XRefs in your files, along with an XRef server, you should be aware that the previous path for volume mounting mentioned in our XRef guide has changed. Previously, /usr/local/apache-tomcat was the suggested path. Now this directory no longer exists and mounting volumes here may result in permission issues.
You should mount your XRefs under /home/tomcat instead now. A path such as /home/tomcat/xRefFiles would work here.
Last updated
Was this helpful?