Skip to main content

Java Server Configurations

  • Updated
Not yet followed by anyone

Java Server Configurations

Logi products work with a variety of Java-based web servers, which often require specific configurations to work correctly and for optimum performance.

The following topics provide the details of these configurations for each server, including:

Please note the following important information:

Oracle has changed its Java usage policies - see Java Usage Policy for important information.

  • The Oracle JDK or OpenJDK 7, 8, 11, 12, 13, or 14 is required for non-Apple platforms, or as noted in individual configuration topics linked above. JDK 7 is required for Apple platforms. The JRE is not sufficient.
  • It's possible to use Logi products on systems that use symbolic links or the Filesystem Hierarchy Standard (FHS), but it makes configuration much more complicated and we don't recommend it.
  • When Logi Studio creates a new application, it's deployed in exploded format within a single "Logi application folder", not as a WAR file. WAR deployments by Studio are not supported at this time.
  • We no longer distribute the ojdbc6.jar. Info Java includes hardcoded references to certain Oracle datatypes, which are referenced in the Oracle JDBC driver. To allow Info Java to compile we included LogiSTUB.jar. This jar replaces ojdbc6.jar, but only to allow Info to run; it does not allow Oracle data to actually be retrieved. To retrieve Oracle data, download ojdbc8.jar and delete LogiSTUB.jar.

JDK/OpenJDK 11 is supported starting with this version but its use requires these configuration steps:

  1. In JVM options, set --illegal-access=permit
  2. In the server's server.xml file, set relaxedQueryChars="[]"
  3. Copy <LogiAppFolder>/rdTemplate/Java11/jaxb-api-2.4.0-b180830.0359.jar to <LogiAppFolder>/WEB-INF/lib.

JDK/OpenJDK 11 and higher are supported starting with Info v12.7 but its use requires these configuration steps:

  1. In JVM options, set --illegal-access=permit and -Dnashorn.args="--no-deprecation-warning"

  2. In the server's server.xml file, set relaxedQueryChars="[]{}|" in the connector elements.

  3. Copy <LogiAppFolder>/rdTemplate/Java11/jaxb-api-2.4.0-b180830.0359.jar to <LogiAppFolder>/WEB-INF/lib

  4. Copy <LogiAppFolder>/rdTemplate/Java11/javax.activation-1.2.0.jar to <LogiAppFolder>/WEB-INF/lib

PhantomJS in Linux, as we distribute, is complete. There is no requirement to install Qt, WebKit, or any other libraries. However, it still relies on Fontconfig (the package Fontconfig or Libfontconfig, depending on the distribution). Normally, this is present; however, if you run PhantomjJS and receive a 127 error you need to complete another step. Navigate to the application root/WEB-INF/lib directory and enter "ldd phantomjs". All the referenced libraries appear. If a version of Fontconfig does not appear then it must be installed. FontConfig installation instructions for various distros vary. The Ubuntu instructions are included here:

sudo apt-get update -y

sudo apt-get install -y fontconfig-config

For more information, see https://phantomjs.org/download and https://www.freedesktop.org/wiki/Software/fontconfig/.

Related articles