This directory contains the configuration files for the standalone server that runs from this installation. All configuration
information for the running server is located here and is the single place for configuration modifications for the stan-
This directory contains the persistent information written by the server to survive a restart of the server.
The end user deployment content can be placed in this directory for automatic detection and deployment of that content
into the server's runtime.
This directory is the location for the installed library Jar files, referenced by the applications using the Extension-List
This directory contains the standalone server logfiles.
This directory contains the location of the temporary files written by the server.
The domain directory structure is quite similar to the standalone equivalent, with one
important difference. As you can see from the following table, the deployments folder
is not present since the domain mode does not support deploying content based on scan-
ning a filesystem. We need to use the WildFly managed instruments (CLI and web admin
console) in order to deploy applications to a domain.
This directory contains the configuration files for the domain Host Controller and any servers running on this installa-
tion. All the configuration information for the servers managed within the domain is located here and is the single place
for configuration information.
This directory is an internal working area for the Host Controller, which controls this installation. This is where it intern-
ally stores the deployment content. This directory is not meant to be manipulated by the end users. It is created after the
first server startup.
This directory is the location where the Host Controller process writes its logs. The Process Controller, a small, light-
weight process that actually spawns other Host Controller processes and any application server processes, also writes
logs here. It is created after the first server startup.
This directory is a writable area used by each application server instance that runs from this installation. Each application
server instance will have its own subdirectory, created when the server is first started. In each server's subdirectory, the
following subdirectories will be present:
Search WWH ::