WildFly Standard Paths: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 3: Line 3:
* [[WildFly Paths#WildFly_Standard_Paths|WildFly Paths]]
* [[WildFly Paths#WildFly_Standard_Paths|WildFly Paths]]
* [[WildFly System Properties]]
* [[WildFly System Properties]]
=Overview=
The values listed under the "" section can be used both as system properties, thus referenced directly in configuration files such as standalone.xml or domain.xml, or as WildFly path names, as values of "relative-to=" attributes.


=Overriding Standard Paths=
=Overriding Standard Paths=

Revision as of 17:46, 7 March 2017

Internal

Overview

The values listed under the "" section can be used both as system properties, thus referenced directly in configuration files such as standalone.xml or domain.xml, or as WildFly path names, as values of "relative-to=" attributes.

Overriding Standard Paths

Standard jboss.server.* paths can be overridden in two ways:

Command Line Arguments

Pass the new values as command line arguments when starting the server:

./standalone.sh -Djboss.server.log=/var/log

JAVA_OPTS

Add the definition to JAVA_OPTS:

JAVA_OPTS="$JAVA_OPTS -Djboss.server.log.dir=/var/log"

Standard Paths

Standard path names, they are "relative-to" roots.

java.ext.dirs

The Java development kit extension directory paths.

jboss.home.dir

The root directory of the WildFly instance.

Example C:/runtime/jboss-eap-6.0.

user.home

The user home directory.

user.dir

The user's current working directory.

java.home

The Java installation directory.

jboss.server.base.dir

The root directory for an individual server instance.

Example C:/runtime/jboss-eap-6.0/profiles/test-profile.

Valid for both standalone mode and domain mode (in which case refers to server node root directory).

jboss.server.data.dir

The directory the server will use for persistent data file storage.

Example C:/runtime/jboss-eap-6.0/profiles/test-profile/data.

Valid for both standalone mode and domain mode (in which case refers to server node data directory).

jboss.server.config.dir

The directory that contains the server configuration.

Example C:/runtime/jboss-eap-6.0/profiles/test-profile/configuration.

Valid for both standalone mode and domain mode (in which case refers to server node configuration directory).

jboss.server.deploy.dir

The directory that contains the server content.

Valid for both standalone mode and domain mode (in which case refers to server node content directory).

Example /opt/jboss-datagrid-7.0.0-server/domain/servers/jdg1/data/content.

jboss.server.log.dir

The directory the server will use for log file storage.

Example C:/runtime/jboss-eap-6.0/profiles/test-profile/log.

Valid for both standalone mode and domain mode (in which case refers to server node log directory).

jboss.server.temp.dir

The directory the server will use for temporary file storage.

Example C:/runtime/jboss-eap-6.0/profiles/test-profile/tmp.

jboss.server.deploy.dir

The directory that the server will use for storing deployed content.

jboss.controller.temp.dir

The directory the host controller will use for temporary file storage.

Example C:/runtime/jboss-eap-6.0/profiles/test-profile/tmp.

jboss.domain.base.dir

The base directory for domain content.

jboss.domain.config.dir

The directory that contains the domain configuration.

jboss.domain.data.dir

The directory that the domain will use for persistent data file storage.

jboss.domain.log.dir

The directory that the domain will use for persistent log file storage.

jboss.domain.temp.dir

The directory that the domain will use for temporary file storage.

jboss.domain.deployment.dir

The directory that the domain will use for storing deployed content.

jboss.domain.servers.dir

The directory that the domain will use for storing outputs of the managed domain instances.