Configuration that only applies to Standalone
Deployments The standalone.xml file includes a section listing the deployment content available for use on the server. Deployment content is made available for use either by uploading it using the AS's management APIs, or by configuring a deployment scanner service and placing the content in the folder scanned by that service (i.e. the deployments/ folder.) Each deployment element includes the following information: name -- Unique identifier of the deployment. Must be unique across all deployments. 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. start -- a boolean flag indicating whether the content is actually deployed into the runtime (and should be automatically deployed when the server starts.)