Skip to content

Quine Enterprise Setup

Prerequisites

Quine Enterprise requires a valid license key to run. To obtain a license key:

Warning

Quine Enterprise authenticates against thatDot servers with your license key, meaning Quine Enterprise requires an open internet connection to authenticate and start. See License Management for network requirements and troubleshooting.

Getting Started with Quine Enterprise

Getting started is easy:

  1. Download and unpack the software - this is an archive (.tar.gz or .zip) holding the Java JAR file quine-enterprise.jar and its lib/ directory. If you would prefer a Docker Container, please contact the thatDot Support team (support@thatdot.com).
  2. Create a configuration file (.conf extension) containing the license key and place it in the unpacked directory, next to quine-enterprise.jar. This is just a plain text file.
  3. Start your instance of Quine Enterprise

Download the Software

After obtaining a license, thatDot will provide you with a secure download link for the Quine Enterprise distribution, quine-enterprise-2.2.1.tar.gz or quine-enterprise-2.2.1.zip. Download it to your local machine or server and unpack it:

tar -xzf quine-enterprise-2.2.1.tar.gz
cd quine-enterprise-2.2.1

The directory holds quine-enterprise.jar, a lib/ directory with every library it depends on, a LICENSE and a README. quine-enterprise.jar loads its libraries from lib/ through its manifest: keep the two together and run it from this directory. Launched without lib/ beside it, quine-enterprise.jar prints lib/ not found beside quine-enterprise.jar; unpack the full distribution and exits.

Create the Configuration File for Quine Enterprise

Create a configuration file containing your license key. This file has a .conf extension and should be placed in the unpacked directory, next to quine-enterprise.jar.

quine {
  license-key = "YOUR_LICENSE_KEY"
}

Start Instance of Quine Enterprise

From the unpacked directory, start Quine Enterprise with your configuration file using the following command (in this example, the file is called quine-enterprise.conf):

java -jar -Dconfig.file=quine-enterprise.conf quine-enterprise.jar

You can also choose to configure your instance on the command line when launching an instance instead of using a configuration file:

java -jar -Dquine.license-key=YOUR_LICENSE_KEY quine-enterprise.jar

Configuring Proxy Settings for Quine Enterprise

When deploying Quine Enterprise in a network environment that requires proxy traversal, you can configure the application to route license server traffic through a proxy server.

Add proxy settings directly to your configuration file:

quine {
  license-key = "YOUR_LICENSE_KEY"
  license-server-proxy-host = "proxy.corp.example.com"
  license-server-proxy-port = 8080
}

Both license-server-proxy-host and license-server-proxy-port must be set for the proxy to activate. See License Management for details.

Note

JVM-level proxy system properties (-Dhttps.proxyHost, etc.) do not apply to license server traffic. You must use the application-level configuration above.

Logging sensitive information

By default, Quine Enterprise will redact sensitive information from logs. If you would like to disable this redaction, you can set the -Dquine.log-config.show-unsafe system property to true to see log redacted information.

Example

java -Dquine.log-config.show-unsafe=true -jar quine-enterprise.jar

Key Resources to Help Guide You

Once you have the software downloaded and the initial configuration file created you are ready to go.

These materials will help you navigate setting up pipelines, querying real-time data, and detecting anomalies.