Java Reference
In-Depth Information
There is no error message after issuing the command; therefore, the application is de-
ployed and activated so that the user can access it. If you want to just perform the deploy-
ment of the application and defer the activation to a later time, you have to add the
--
disabled
switch, as shown in the following command line:
[standalone@localhost:9990 /] deploy ../HelloWorld.war
--disabled
In order to activate the application, simply issue another
deploy
shell command without
the
--disabled
switch, as shown in the following command line:
[standalone@localhost:9990 /] deploy --name=HelloWorld.war
Redeploying the application requires an additional flag for the
deploy
shell command.
Use the
-f
argument to force the application's redeployment, as shown in the following
command line:
[localhost:9990 /] deploy -f ../HelloWorld.war
Undeploying the application can be done with the
undeploy
command, which takes the
application that is deployed as an argument. This is shown in the following command line:
[localhost:9990 /] undeploy HelloWorld.war
Deploying applications to a domain
Deploying applications when running in the domain mode is slightly different from doing
this in the standalone mode. The difference boils down to the fact that an application can
be deployed just to one server group or to all the server groups. As a matter of fact, one
reason why you might split your domain into different server groups might be that you are
planning to offer different types of services (and hence applications) to each server group.
So, in order to deploy your
HelloWorld.war
application to all server groups, issue the
following command:
[domain@localhost:9990 /] deploy HelloWorld.war
--all-server-groups
