WildFly Exploded Deployments with CLI: Difference between revisions
Jump to navigation
Jump to search
| 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. | ||
==Trigger the Deployment via CLI== | |||
Connect the CLI to the application server instance. | |||
Revision as of 23:19, 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.
Trigger the Deployment via CLI
Connect the CLI to the application server instance.