It's possible to perform internal changes to WebViewer Server, though we do not recommend it. You may wish to do this if our options do not expose a particular configuration setting, such as the maximum allowed threads in Tomcat.
This section will help you understand WebViewer Server. Below is how you would typically build on top of our existing container.
The important paths within the server image are as follows:
/usr/local/apache-tomcat
: This is the server which hosts the WebViewer Server code, it is where the bulk of work occurs.
/usr/local/apache-tomcat/conf
: This is the main configuration directory for tomcat, within you'll find 3 configuration files - server.xml, web.xml and context.xml. You may change this but do so at your own risk as we have configured these files specifically for WebViewer Server.
/usr/local/apache-tomcat/static_data
: This is where we store WebViewer Server's cache.
/usr/local/apache-tomcat/internal_data/
: Where temporary data is stored, mainly used by Apryse core for memory swaps.
/usr/local/apache-tomcat/webapps
: This contains the blackbox and demo webapps. Prior to 1.5.6 this will contain Java classes, in any other version it will contain .war
files containing the webapps.
/usr/local/apache-tomcat/logs
: Contains all logging data for WebViewer Server.
When WebViewer Server starts, it executes a script located in /usr/local/apache-tomcat/bin/watchdog.sh
, this file is responsible for keeping Tomcat running inside of the container.
For more information on configuring Tomcat, you can refer to their available guide for Tomcat 10 http://tomcat.apache.org/tomcat-10.0-doc/
If you need to update WebViewer Server's core libraries, you can do so.
For Windows, you need to copy PDFNetC.dll to /install_dir/apache-tomcat/bin/
.
Some customers may need to modify JAVA_OPTS, most likely to change memory values. This can be easily done by setting the JAVA_OPTS environment variable. Keep in mind the following must be in the JAVA_OPTS variable.
In the docker-compose this would be defined like so:
The main use for this is to modify Java memory limits. We recommend setting Xmx to a bit less than your server's available memory. This will prevent Java from exceeding allocation limits because it has not garbage collected.
The following documentation details more about these java options.
https://docs.oracle.com/javase/8/docs/technotes/tools/windows/java.html
Adding custom TTF and OTF fonts to WebViewer Server is easy, although how to do so depends on how you are running it.
It is possible to add TTF and OTF fonts to WebViewer Server without rebuilding its container. To do so, mount your custom fonts as a volume to /home/tomcat/.fonts/custom
. This can be done with docker-compose, as shown with the following line:
You can replace ./myfonts
with whatever path contains your fonts.
Alternatively, this can also be done when running directly through Docker, like so:
Similarly, /home/user/myfonts
is a stand-in for the path to your fonts. Also, you should run your Docker setup with a clean start before you mount a volume.
You can also add TTF and OTF fonts by modifying the container image. You can replace myfonts/
with whatever path contains your fonts.
On Windows, you should install TTF and OTF fonts directly onto your system, and then restart WebViewer Server. This guide from Microsoft goes into more detail on how this is done.
If a module you are running supports other types of fonts, such as SHX and RTF fonts for the CAD Module, it possible to add your own custom fonts for those modules to WebViewer Server.
To add module-specific fonts to WebViewer Server without rebuilding its container, mount your custom fonts as a volume to /usr/local/apache-tomcat/fonts
. This can be done with docker-compose, as shown with the following line:
You can replace ./myfonts
with whatever path contains your fonts.
Alternatively, this can also be done when running directly through Docker, like so:
Similarly, /home/user/myfonts
is a stand-in for the path to your fonts. Also, you should run your Docker setup with a clean start before you mount a volume.
You can also add module-specific fonts to WebViewer Server by modifying its container image. myfonts/
can be replaced with whatever path contains your custom fonts.
You must manually add module-specific fonts within your WebViewer Server directory on Windows. You can add your custom fonts to \WebViewer-Server\apache-tomcat\fonts
, where \WebViewer-Server
is your root directory for WebViewer Server. You may need to create the \fonts
folder yourself.
Did you find this helpful?
Trial setup questions?
Ask experts on DiscordNeed other help?
Contact SupportPricing or product questions?
Contact Sales