WildFly Deployment Concepts: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
Line 8: Line 8:
=Standalone Mode Deployments=
=Standalone Mode Deployments=


==Location of the Deployment Artifacts on the File System==
==Location of the Deployment Artifacts on the File System in Standalone Mode==


==Standalone Deployment Modes==
==Standalone Deployment Modes==
Line 58: Line 58:
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}}


==Domain Deployment Modes==
==Location of the Deployment Artifacts on the File System in Domain Mode==
 
* CLI
* Management Console
* HTTP REST
 
==Location of the Deployment Artifacts on the File System==


For the location of the domain-wide artifact repository, see [[#Deployment_Artifact_Repository|Deployment Artifact Repository]] section below.  
For the location of the domain-wide artifact repository, see [[#Deployment_Artifact_Repository|Deployment Artifact Repository]] section below.  
Line 71: Line 65:


  $JBOSS_HOME/domain/data/servers/''<server-node-name>''/content/''<first-two-characters-of-the-hash>''/''<the-rest-of-the-hash>''/content
  $JBOSS_HOME/domain/data/servers/''<server-node-name>''/content/''<first-two-characters-of-the-hash>''/''<the-rest-of-the-hash>''/content
==Domain Deployment Modes==
* CLI
* Management Console
* HTTP REST


==Rollout Plans==
==Rollout Plans==

Revision as of 14:43, 20 September 2017


Migrating from https://home.feodorov.com:9443/wiki/Wiki.jsp?page=JBoss7Deployment

Internal

Standalone Mode Deployments

Location of the Deployment Artifacts on the File System in Standalone Mode

Standalone Deployment Modes

  • CLI
  • Management Console
  • HTTP REST
  • Deployment Scanner

Domain Mode Deployments

Deployment Mechanics

Deployment artifacts are

Domain-Wide 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

WildFly CLI Deployment/Undeployment

Location of the Deployment Artifacts on the File System in Domain Mode

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

Domain Deployment Modes

  • CLI
  • Management Console
  • HTTP REST

Rollout Plans

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Administration_and_Configuration_Guide/sect-Rollout_Plan.html

Deployment Artifact Repository

Deployment Scanner

Deployment Scanner

Deployment Descriptor Validation

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Administration_and_Configuration_Guide/chap-Application_Deployment.html#About_Application_Deployment1
./domain.sh|./standalone.sh -Dorg.jboss.metadata.parser.validate=true