WildFly Deployment Concepts: Difference between revisions
Jump to navigation
Jump to search
Migrating from https://home.feodorov.com:9443/wiki/Wiki.jsp?page=JBoss7Deployment
Line 54: | Line 54: | ||
Also see {{Internal|WildFly CLI - Deployment and Undeployment#Overview|WildFly CLI Deployment/Undeployment}} | Also see {{Internal|WildFly CLI - Deployment and Undeployment#Overview|WildFly CLI Deployment/Undeployment}} | ||
=Deployment Scanner= | |||
{{Internal|WildFly Deployment Scanner|Deployment Scanner}} |
Revision as of 14:16, 20 September 2017
Internal
Standalone Mode Deployments
Location of the Deployment Artifacts on the File System
Domain Mode Deployments
Location of the Deployment Artifacts on the File System
For the location of the domain-wide artifact repository, see Deployment Artifact Repository section below.
In case of server nodes, copies of the deployment artifacts are pushed by the domain management logic to:
$JBOSS_HOME/domain/data/servers/<server-node-name>/content/<first-two-characters-of-the-hash>/<the-rest-of-the-hash>/content
Deployment Artifact Repository
The domain-wide deployment artifact repository is located on the controller host, under $JBOSS_HOME/domain/data/content. The content is maintained in a two-level directory structure named based on the content's hash. The names of the first level directories consist of the first two characters of content hashes. A second-level directory name contains the rest of the hash, and the directory contains the content itself, as a file named "content".
Example:
<domain ...>
...
<deployments>
...
<deployment name="test-servlet.war" runtime-name="test-servlet.war">
<content sha1="e85e00cddbae1752cb7eaaa73adb1eed09787d70"/>
</deployment>
</deployments>
</domain>
$JBOSS_HOME/domain/data/content/<first-two-characters-of-the-hash>/<the-rest-of-the-hash>/content
domain | +-- data | +-- content | +-- e8 | +-- 5e00cddbae1752cb7eaaa73adb1eed09787d70 | +-- content
Also see