Show Table of Contents
2.3. Filesystem Paths
2.3.1. Filesystem Paths
JBoss EAP 6 uses logical names for a filesystem paths. The
standalone.xmlconfigurations all include a section where paths can be declared. Other sections of the configuration can then reference those paths by their logical name, avoiding the declaration of the absolute path for each instance. This benefits configuration and administration efforts as it allows specific host configurations to resolve to universal logical names.
For example, the logging subsystem configuration includes a reference to the
jboss.server.log.dirpath that points to the server's
Example 2.10. Relative path example for the logging directory
<file relative-to="jboss.server.log.dir" path="server.log"/>
JBoss EAP 6 automatically provides a number of standard paths without any need for the user to configure them in a configuration file.
Table 2.2. Standard Paths
| ||The root directory of the JBoss EAP 6 distribution.|
| ||The user home directory.|
| ||The user's current working directory.|
| ||The Java installation directory|
| ||The root directory for an individual server instance.|
| ||The directory the server will use for persistent data file storage.|
| ||The directory the server will use for log file storage.|
| ||The directory the server will use for temporary file storage.|
| ||The directory under which a host controller will create the working area for individual server instances in a managed domain.|
Users can add their own paths or override all except the first five of the above by adding a
pathelement to their configuration file. The following example shows a new relative path declaration relative to the root directory for the individual server instance.
Example 2.11. Format of a relative path
<path name="examplename" path="example/path" relative-to="jboss.server.data.dir"/>
The structure of a path declaration uses the following attributes.
Table 2.3. Path Attributes
| ||The name of the path.|
| || The actual filesystem path. Treated as an absolute path, unless the |
| ||An optional attribute indicating the name of another previously named path, or of one of the standard paths provided by the system.|
pathelement in a
domain.xmlconfiguration file only requires the name attribute. It does not need to include any information indicating what the actual filesystem path is, as shown in the following example.
Example 2.12. Domain path example
This configuration simply declares that there is a path named
examplethat the other parts of the
domain.xmlconfiguration can reference. The actual filesystem location declared by
exampleis specific to the respective
host.xmlconfiguration files of the host instances joining the domain groups. If this approach is used, there must be a path element in each machine's
host.xmlthat specifies what the actual filesystem path is.
Example 2.13. Host path example
<path name="example" path="path/to/example" />
pathelement in a
standalone.xmlmust include the specification of the actual filesystem path.