WildFly Standard Paths: Difference between revisions
| (9 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
* [[WildFly Paths#WildFly_Standard_Paths|WildFly Paths]] | * [[WildFly Paths#WildFly_Standard_Paths|WildFly Paths]] | ||
* [[WildFly System Properties]] | |||
=Overview= | |||
The values listed under the "[[#Standard_Paths|Standard Paths]]" section can be used both as ''system property names'', thus referenced directly in configuration files (standalone.xml and domain.xml), or as WildFly ''path names''. As path names, they can be used as values of "<tt>[[WildFly Paths#relative-to|relative-to]]</tt>" attributes, where they have a "root path" semantics. | |||
=Overriding Standard Paths= | =Overriding Standard Paths= | ||
| Line 25: | Line 30: | ||
=Standard Paths= | =Standard Paths= | ||
==java.ext.dirs== | ==java.ext.dirs== | ||
| Line 54: | Line 58: | ||
Example <tt>C:/runtime/jboss-eap-6.0/profiles/test-profile</tt>. | Example <tt>C:/runtime/jboss-eap-6.0/profiles/test-profile</tt>. | ||
Valid for both standalone mode and domain mode (in which case refers to server node root directory). | |||
==jboss.server.data.dir== | ==jboss.server.data.dir== | ||
| Line 60: | Line 66: | ||
Example <tt>C:/runtime/jboss-eap-6.0/profiles/test-profile/data</tt>. | Example <tt>C:/runtime/jboss-eap-6.0/profiles/test-profile/data</tt>. | ||
Valid for both standalone mode and domain mode (in which case refers to server node data directory). | |||
==jboss.server.config.dir== | ==jboss.server.config.dir== | ||
| Line 66: | Line 74: | ||
Example <tt>C:/runtime/jboss-eap-6.0/profiles/test-profile/configuration</tt>. | Example <tt>C:/runtime/jboss-eap-6.0/profiles/test-profile/configuration</tt>. | ||
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 <tt>/opt/jboss-datagrid-7.0.0-server/domain/servers/jdg1/data/content</tt>. | |||
==jboss.server.log.dir== | ==jboss.server.log.dir== | ||
| Line 72: | Line 90: | ||
Example <tt>C:/runtime/jboss-eap-6.0/profiles/test-profile/log</tt>. | Example <tt>C:/runtime/jboss-eap-6.0/profiles/test-profile/log</tt>. | ||
Valid for both standalone mode and domain mode (in which case refers to server node log directory). | |||
==jboss.server.temp.dir== | ==jboss.server.temp.dir== | ||
Latest revision as of 17:49, 7 March 2017
Internal
Overview
The values listed under the "Standard Paths" section can be used both as system property names, thus referenced directly in configuration files (standalone.xml and domain.xml), or as WildFly path names. As path names, they can be used as values of "relative-to" attributes, where they have a "root path" semantics.
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
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.