Deployments in domain.xml
Deployments The Domain Controller maintains a repository of deployment content that is available for use in the servers in the domain. The domain.xml file includes a section listing the deployment content available for use in the domain. Deployment content is made available for use by uploading it using the AS's management APIs. Each deployment element includes the following information: name -- Unique identifier of the deployment. Must be unique across all deployments in the domain. runtime-name -- name by which the deployment should be known within the runtime. This would be equivalent to the file name of a deployment file, and would form the basis for such things as default Java Enterprise Edition application and module names. This would typically be the same as name, but in some cases users may wish to have two deployments with the same runtime-name may (e.g. two versions of "foo.war") both available in the deployment content repository, in which case the deployments would need to have distinct name values but would have the same runtime-name hash -- a hash of the deployment content, created by the server when the content was uploaded. The server uses the hash internally to find content in the repository. Note that the fact that a deployment is listed in the domain-level deployments listing does not mean it will actually be deployed on any servers. It simply means its content is known to the domain and available for use. Deployments are only deployed on servers when they are mapped to server groups (see below).