Java Reference
In-Depth Information
Deploying applications using the command-line
interface
Another way to deploy an application is via the WildFly
Command-line Interface
(
CLI
),
which can be started from
jboss-cli.bat
(or
jboss-cli.sh
for Linux users). Don't
be afraid of using a textual interface to manage your application server; as a matter of fact,
the console provides built-in autocomplete features and you can display the available com-
mands at any time by simply hitting the
Tab
key, as shown in the following screenshot:
As you might have guessed, in order to deploy an application, you need to issue the
de-
ploy
shell command. When used without arguments, the
deploy
shell command
provides a list of applications that are currently deployed. Refer to the following code:
[standalone@localhost:9990 /] deploy
ExampleApp.war
If you feed a resource archive such as
.war
to shell, it will deploy it on the standalone
server right away, as shown in the following command line:
[standalone@localhost:9990 /] deploy ../HelloWorld.war
As you can see from the preceding command line, the CLI uses the folder where your de-
ployments were actually launched at its initial location, which is
JBOSS_HOME/bin
by
default. You can, however, use absolute paths when specifying the location of your
archives; the CLI expansion facility (using the
Tab
key) makes this option fairly simple.
This is demonstrated in the following command line:
[standalone@localhost:9990 /] deploy
c:\deployments\HelloWorld.war
