Java Reference
In-Depth Information
[standalone@localhost:9999 /]
/subsystem=deployment-scanner/
scanner=default:read-attribute(
include-defaults= name=
Choose the parameter you want and specify its value after
=
. Finally, when all the
parameters have been specified, add
)
and press
Enter
to issue the command.
Deploying applications using the CLI
Deploying an application (in the standalone mode) can be easily performed by copy-
ing the application's archives into the
deployment
folder of your server distribution.
That's a pretty handy option; however, we would like to stress on the advantage of
using the CLI interface, which offers a wide choice of additional options when de-
ploying, and also provides the opportunity to deploy applications remotely.
All it takes to deploy an application's archive is a connection to the management
instance, either local or remote, and by issuing the
deploy
shell command. When
used without arguments, the
deploy
command provides the list of applications that
are currently deployed, as shown in the following command:
[disconnected /] connect
Connected to standalone controller at
localhost:9999
[localhost:9999 /] deploy
ExampleApp.war
If you feed a resource archive such as a WAR file to the shell, it will deploy it on the
standalone server right away:
[standalone@localhost:9999 /] deploy ../
MyApp.war 'MyApp.war' deployed successfully.
By default, the CLI uses the
JBOSS_HOME/bin
file as a source for your deployment
archives. You can however, use absolute paths when specifying the location of your
