|Home > Documentation > User's guide > Administration > Administrative Tasks > Administering applications > Starting and stopping application modules|
You can change the status of an application in two different ways. You can use the Deployer tool or the Geronimo Administration Console.
The Deployer tool has many commands. In Installing and removing applications section we have explored mainly deploy and undeploy and very briefly list-modules. This section is going to focus on the latter command to retrieve the name of the module we want to change the status and will introduce two new commands, start and stop. Later we will discuss the use of the Geronimo Administration Console as the alternative method.
The list-module command accepts the following tree parameters:
You can also specify a target at the end of the command. This option is rarely used since most of the time you will have only one configuration store defined on each server. If no targets are specified, then modules on all targets will be listed, otherwise only modules on the specified targets.
This is useful to identify the status of a particular module and the module ID itself. We will use this command to identify the HelloWorld application and change its status.
From a command line window run the following command from the <geronimo_home>\bin directory to list all the modules:
deploy --user system --password manager list-modules
You will receive a list of all the modules installed on the server. Note that the started modules are differentiated by a + sign on the left and are displayed first in the list.
Our target now is "
+ sample.applications/HelloWorldApp/2.0/war @ http://hcunico:8080/hello " , this module's status is started since there is a + on the left. Alternatively, you can run the following command to list just the started modules:
deploy --user system --password manager list-modules --started
To stop the "
sample.applications/HelloWorldApp/2.0/war module type the following command:
deploy --user system --password manager stop sample.applications/HelloWorldApp/2.0/war
You will receive a confirmation message similar to the one listed below indicating that the module has been stopped.
When you list all the stopped modules you should now see added to the list the
sample.applications/HelloWorldApp/2.0/war module. See the command and results in the following example.
To start the modules just use start instead of stop.
deploy --user system --password manager start sample.applications/HelloWorldApp/2.0/war
You will receive a confirmation message similar to the one listed below indicating that the module has been started.
As an alternative to the command line option you can use the Geronimo Administration Console to change the status of the modules. Open the Geronimo Administration Console and navigate to Applications on the Console Navigation menu on the left hand side. There you will find Application EARs and Web App WARs, depending on the type of application you want to change the status, you will choose either Application EARs or Web App WARs. For this example we continue to use HelloWorld.war as the sample application, hence we will select Web App WARs.
We used this portlet in the Installing and removing applications section to install and remove applications via the Geronimo Administration Console. From this same portlet you can also change the status of the applications. The available commands within the portlet will change depending on the status for each application. If the application is in running status (started), the commands Stop and Restart will be displayed. If the application is stopped, only the command Start will be displayed. The Uninstall command will always be displayed independently of the status of the application. To change the status of the application just click on the command (Start or Stop).