WildFly 10.1 Model Reference

  1. WildFly 10.1
  2. deployment

A deployment represents anything that can be deployed (e.g. an application such as EJB-JAR, WAR, EAR, any kind of standard archive such as RAR or JBoss-specific deployment) into a server.

Children (2)

  • subdeployment Runtime resources associated with a child deployment packaged inside another deployment; for example a war packaged inside an ear.
  • subsystem Runtime resources created when the deployment is deployed, organized by the subsystem responsible for the runtime resource.
    • batch-jberet Information about the batch subsystem for the deployment.
    • datasources The data-sources subsystem, used to declare JDBC data-sources
    • ejb3 Runtime resources exposed by EJBs components included in this deployment.
    • jaxrs The configuration of the JAX-RS subsystem.
    • jpa The configuration of the JPA subsystem.
    • logging Information about the logging configuration for this deployment. Note that this may not be accurate if the deployment is using some other means of configuring a log manager such as logback. The resolved configuration is what loggers not covered by the deployments specific log manager would use.
    • messaging-activemq Runtime resources exposed by messaging resources included in this deployment.
    • undertow A deployment
    • webservices Runtime resources exposed by web service components in the deployment.

Attributes (11)

  • content List of pieces of content that comprise the deployment.
    • Attribute Value
    Type LIST
    Nillable false
    Expressions Allowed false
    Storage configuration
    Access Type read-only
  • disabled-time Last time the application was disabled
    • Attribute Value
    Type LONG
    Nillable true
    Expressions Allowed false
    Unit MILLISECONDS
    Storage runtime
    Access Type read-only
  • disabled-timestamp Last timestamp the application was disabled. Format is yyyy-MM-dd HH:mm:ss,SSS zzz.
    • Attribute Value
    Type STRING
    Nillable true
    Expressions Allowed false
    Storage runtime
    Access Type read-only
  • enabled Boolean indicating whether the deployment content is currently deployed in the runtime (or should be deployed in the runtime the next time the server starts.)
    • Attribute Value
    Default Value false
    Type BOOLEAN
    Nillable true
    Expressions Allowed false
    Storage configuration
    Access Type read-only
  • enabled-time Last time the application was enabled
    • Attribute Value
    Type LONG
    Nillable true
    Expressions Allowed false
    Unit MILLISECONDS
    Storage runtime
    Access Type read-only
  • enabled-timestamp Last timestamp the application was enabled. Format is yyyy-MM-dd HH:mm:ss,SSS zzz.
    • Attribute Value
    Type STRING
    Nillable true
    Expressions Allowed false
    Storage runtime
    Access Type read-only
  • name Unique identifier of the deployment. Must be unique across all deployments.
    • Attribute Value
    Type STRING
    Nillable false
    Expressions Allowed false
    Storage configuration
    Access Type read-only
  • owner Address of a resource that has indicated it controls the lifecycle of this deployment (e.g. a deployment scanner resource.) Will be undefined if no resource claimed ownership when the deployment was added.
    • Attribute Value
    Type LIST
    Nillable true
    Expressions Allowed false
    Storage configuration
    Access Type read-only
  • persistent Boolean indicating whether the existence of the deployment should be recorded in the persistent server configuration. Only relevant to a standalone mode server. Default is 'true'. A deployment managed by a deployment scanner would have this set to 'false' to ensure the deployment is only deployed at server start if the scanner again detects the deployment.
    • Attribute Value
    Type BOOLEAN
    Nillable false
    Expressions Allowed false
    Storage configuration
    Access Type read-only
  • runtime-name Name by which the deployment should be known within a server's 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' (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'.
    • Attribute Value
    Type STRING
    Nillable false
    Expressions Allowed false
    Storage configuration
    Access Type read-only
  • status The current runtime status of a deployment. Possible status modes are OK, FAILED, and STOPPED. FAILED indicates a dependency is missing or a service could not start. STOPPED indicates that the deployment was not enabled or was manually stopped.
    • Attribute Value
    Type STRING
    Nillable true
    Expressions Allowed false
    Storage runtime
    Access Type metric

Operations (5)

  • add Adds previously uploaded content to the list of content available for use. Does not actually deploy the content unless the 'enabled' parameter is 'true'.
    Request Parameter Type Required Expressions Allowed Default value Description
    runtime-name STRING false false Name by which the deployment should be known within a server's 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' (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'.
    content LIST false false List of pieces of content that comprise the deployment.
    enabled BOOLEAN false false false Boolean indicating whether the deployment content is currently deployed in the runtime (or should be deployed in the runtime the next time the server starts.)
  • deploy Deploy the specified deployment content into the runtime, optionally replacing existing content.
  • redeploy Undeploy existing content from the runtime and deploy it again.
  • remove Remove a deployment from the list of content available for use. If the deployment is currently deployed in the runtime it will first be undeployed.
  • undeploy Undeploy content from the runtime. The content remains in the list of content available for use.