WildFly Exploded Deployments with CLI: Difference between revisions
| Line 12: | Line 12: | ||
Expand the JEE archive. The archive can be expanded in any local directory accessible to the application server, not necessarily under the <tt>deployments</tt> directory. | Expand the JEE archive. The archive can be expanded in any local directory accessible to the application server, not necessarily under the <tt>deployments</tt> directory. | ||
Expanding the archive in the deployment directory works but care must be taken not to interfere with the deployment scanner that monitors that directory. | |||
==Trigger the Deployment via CLI== | ==Trigger the Deployment via CLI== | ||
Revision as of 23:28, 31 March 2016
Internal
Overview
Exploded deployments are not deployed by default by a WildFly instance. They can be triggered by configuring the deployment scanner, using marker files or via CLI. The procedure to trigger the deployment with CLI is described below.
Procedure
"Explode" the JEE archive
Expand the JEE archive. The archive can be expanded in any local directory accessible to the application server, not necessarily under the deployments directory.
Expanding the archive in the deployment directory works but care must be taken not to interfere with the deployment scanner that monitors that directory.
Trigger the Deployment via CLI
Connect the CLI to the application server instance. For more details on how to connect CLI see Connect to a Controller.
Trigger the deployment with the following command, providing appropriate values to the "runtime-name" and the "path" attributes.
[standalone@localhost:9999 /] /deployment=test:add(runtime-name="test.ear", enabled=true, content=[{"path"=>"/Users/ovidiu/runtime/jboss-eap-6.4/profiles/msc/deployments/mBanking.ear", "archive"=>false}])