Skip to main content
Version: 8.2405.x.x RR

Deployment types

nevisMeta is implemented as a web service in Java.

In case of a standalone deployment, nevisMeta is deployed as a web service including an embedded container.

The following sections describe the deployment types and their configuration.


The standalone deployment type makes use of an embedded container. There is no need anymore to install a separate container application. The standalone deployment mode is the default.

The following configuration files control the behavior of nevisMeta in the standalone deployment type:

Configuration file: env.conf

  • Remarks:

Administration command and process environment:

  • JAVA_HOME (optional): Use specified JRE/JD. KNo other parameter should be changed.

    • Heap size
    • Garbage collector
    • JSSE configuration properties
    • JNDI configuration properties
    • Temporary Directory
  • JAVA_OPTS: JVM command-line options

The JAVA_OPTS environment variable can be an expression that will be replaced.

Example 1: (using single quotes)

'${exec:cat /var/opt/pwd.txt}'

Example 2: (using double quotes)

"\${exec:cat /var/opt/pwd.txt}"

Old string syntax: (cannot handle spaces in jvm arguments and inline comments)

JAVA_OPTS="-server \\${exec:cat /var/opt/pwd.txt}"

In case if you use double quotes the $ must be escaped. For details, see Standalone expression.

Configuration file:

Application, login, server configuration:

  • Back-end configuration options
  • Ninja authentication module configuration options
  • Scaling (concurrency with worker threads)
  • Network settings (host, port, protocol, tls, ...)

Configuration file: log4j.xml

Logging configuration:

  • Configuration of log levels for for individual components
  • Audit channel (if the file rotation policy or output file needs to be customized)

The configuration files are located here:

  • /var/opt/nevismeta/<instance>/conf

The location of the temporary files of the standalone embedded container can be changed by -[]( This property can be provided via JAVA_OPTS in the env.conf.

Environment configuration

As the first priority, nevisMeta uses the Java installation defined in the file env.conf using the configuration property JAVA_HOME. If the JAVA_HOME property is not defined in the file env.conf, the Java version as defined in the PATH environment variable is used.

To define the usage of a specific Java installation, we recommend setting the configuration property JAVA_HOME in the file env.conf:



Server configuration properties

You can configure the server of the standalone deployment type through the properties in the file (see the following table).

Example: <instance>


Example: https

Default: https


Example: 8991

Default: 8991

Example: localhost


Example: /var/opt/keybox/default/node_keystore.jks


Example: keystorepassword


Example: /var/opt/keybox/default/truststore.jks


Example: truststorepassword


Example: true

Default: false


Example: required

Default: requested

server.tls.verify-hostname (optional)

Example: true

Default: false


Example: TLSv1.2

Default: TLSv1.2





Example: 200

Default: 200


Example: 6000

Default: 6000


Example: 9000

Default: 9000


Example: false

Default: false


Example: true

Default: false


Example: false

Default: false

Example: false

Default: true

Example: false

Default: true

Example: true

Default: true


Example: 30000

Default: 30000


Example: 600000

Default: 600000


Example: 1800000

Default: 1800000


Example: 10

Default: 10


Example: 1000

Default: 10


The maximum number of cached query plans. For more details, see:

Example: 512

Default: 2048


By default, the IN clause expands to include all bind parameter values. However, for database systems supporting execution plan caching, there's a better chance of hitting the cache if the number of possible IN clause parameters lowers. For this reason, we can expand the bind parameters to power-of-two: 4, 8, 16, 32, 64. This way, an IN clause with 5, 6, or 7 bind parameters will use the 8 IN clause, therefore reusing its execution plan. If you want to activate this feature, you need to set this property to true. For more details, see:

Example: true

Default: false

Standalone - configuration file

The property values related to the server configuration in the file can be expressions that will be replaced. The next table shows the available syntax:

${exec:command}server.tls.keystore-passphrase: ${exec:/var/opt/keys/own/instance/} ${exec:hostname -f}Executes the given command and uses its output as the value
${env:variablename} ${env:HOSTNAME}Uses the value of the specified environment variable.

Standalone server command-line interface

For standalone deployments, the standalone command-line interface (CLI) provides a low level interface to run the server process. It can be used by higher level tools like the administrative CLI (see The administrative command-line interface) or by the user directly.

You can use the standalone CLI to start nevisMeta without involvement of other system components like for example systemd.

You find the standalone script at /opt/nevismeta/bin/nevismeta-server. It provides the following command-line options:

Command-line argumentRemarksDefault
-c, --config PATHRequired. Path to the configuration file default.
-n, --name NAMEUnique name for that Nevis component node.Overrides the value of the property (in the file).See the property in the file.
-p, --port PORTThe HTTP/S port to listen on. TLS must be configured in the config file and not as an argument.Overrides the value of the property server.port (in the file).See the server.port property in the file.
-H, --host HOSTThe HTTP/S host to bind on. By default binds on all IPv4 and IPv6 interfaces.Overrides the value of the property (in the file).See the property in the file.
--log-config PATHLog configuration file to be used.If a log configuration is provided, nevisMeta will use the given configuration file to determine how logging should behave. If no configuration file is provided, nevisMeta will log to the console by default.Not set.
-V, --versionDisplay version and exit with status code 0.
-h, --helpShow complete and detailed usage and exit with status code 0.

Command-line arguments always prevail over the configuration in the file!

Example usage of the standalone CLI

To start an existing nevisMeta instance named "default" without using systemd to manage the service, set the following commands:

# set working directory
cd /var/opt/nevismeta/default

/opt/nevismeta/bin/nevismeta-server --config /var/opt/nevismeta/default/conf/ --log-config /var/opt/nevismeta/default/conf/log4j.xml

Creating Self-Signed Certificates with SAN (Subject Alternative Names)

The following commands generate certificates that can be used in a test environment using a nevisAuth instance with 2-way client authentication and hostname verification enabled.

The keytool command creates a PKCS12 keystore with two SANs (one of type DNS, the other of type IP) and then, using openssl, we generate a PEM file from it, to be used by nevisProxy, for example.

# keytool -genkeypair -keyalg RSA -alias nevisProxyClientCert -keystore /var/opt/certs/keystore.p12 -storetype pkcs12 -storepass password -validity 360 -keysize 2048 -dname ",ou=auth,o=o=nevis-security,dc=com" -noprompt -ext,ip:
# openssl pkcs12 -in /var/opt/certs/keystore.p12 -nodes -out /var/opt/certs/keystore.pem

The following command creates a keystore with two SANs using openssl. Note that both server.key and server.crt are PEM formatted.

openssl genrsa -out /var/opt/certs/ca.key 2048
openssl req -new -x509 -days 365 -key /var/opt/certs/ca.key -subj "/DC=COM/O=nevis-security/OU=auth/" -out /var/opt/certs/ca.crt

openssl req -newkey rsa:2048 -nodes -keyout /var/opt/certs/server.key -subj "/DC=COM/O=nevis-security/OU=auth/" -out /var/opt/certs/server.csr
openssl x509 -req -extfile <(printf ",,IP:") -days 365 -in /var/opt/certs/server.csr -CA /var/opt/certs/ca.crt -CAkey /var/opt/certs/ca.key -CAcreateserial -out /var/opt/certs/server.crt