Apache Geronimo provides several tools for administering the server. These tools are available via command line and some via a Web based console. The Web based Geronimo console is explained in detail in the following section Geronimo Administration Console. The currently available command line tools are located in the <geronimo_home>/bin directory and are enumerated in the following list:

Although the tools name is self-explanatory, it may not be the same case with the tool's parameters. The following sections explain more in detail these tools and commands usage.

startup

This command is certainly used to start the Apache Geronimo server. You can start the Apache Geronimo server in two different ways by running the following commands:

<geronimo_home>/bin/java -jar server.jar

or simply

<geronimo_home>/bin/startup

The startup command invokes the server.jar.

In both cases this command accepts the same parameters. The available parameters are:

--quiet
Suppress the normal startup progress bar. This is typically used when redirecting console output to a file, or starting the server from an IDE or other tool.

--long
Write startup progress to the console in a format that is suitable for redirecting console output to a file, or starting the server from an IDE or other tool (does not use linefeeds to update the progress information that is used by default if you do not specify --quiet or --long).

-v --verbose
Sets the console log level to INFO, resulting in more console output than is normally present.

-vv --veryverbose
Sets the console log level to DEBUG, resulting in even more console output.

-override [configId]
Overrides the configurations in <geronimo_home>/var/config.list such that only the configurations listed on the command line will be started. Note that many J2EE
features depend on certain configs being started, so you should be very careful what you omit. Any arguments after -override are assumed to be configuration names.

When you run this command from a Microsoft Windows command line that window will get locked with the startup results screen. On a Linux based operating system you can run this command in background getting back the control for this window terminal.

If you run the startup command without any parameters you will see a screen similar to this one.

Booting Geronimo Kernel (in Java 1.4.2_09)...
Configuration geronimo/rmi-naming/1.1/car started in  1/20   1s
Configuration geronimo/j2ee-server/1.1/car started in  2/20   1s
Configuration geronimo/j2ee-security/1.1/car started in  3/20   2s
Configuration geronimo/axis/1.1/car started in  4/20   0s
Configuration geronimo/openejb/1.1/car started in  5/20   0s
Configuration geronimo/system-database/1.1/car started in  6/20  14s
Configuration geronimo/activemq-broker/1.1/car started in  7/20   5s
Configuration geronimo/activemq/1.1/car started in  8/20   1s
Configuration geronimo/tomcat/1.1/car started in  9/20   4s
Configuration geronimo/geronimo-gbean-deployer/1.1/car started in 10/20   1s
Configuration geronimo/j2ee-deployer/1.1/car started in 11/20   0s
Configuration geronimo/openejb-deployer/1.1/car started in 12/20   0s
Configuration geronimo/client-deployer/1.1/car started in 13/20   0s
Configuration geronimo/axis-deployer/1.1/car started in 14/20   0s
Configuration geronimo/sharedlib/1.1/car started in 15/20   0s
Configuration geronimo/tomcat-deployer/1.1/car started in 16/20   0s
Configuration geronimo/welcome-tomcat/1.1/car started in 17/20   0s
Configuration geronimo/webconsole-tomcat/1.1/car started in 18/20   4s

Configuration geronimo/remote-deploy-tomcat/1.1/car started in 19/20   0s
Configuration geronimo/hot-deployer/1.1/car started in 20/20   0s
Startup completed in 39 seconds
  Listening on Ports:
    1099 0.0.0.0   RMI Naming
    1527 0.0.0.0   Derby Connector
    4201 0.0.0.0   ActiveIO Connector EJB
    4242 127.0.0.1 Remote Login Listener
    8009 0.0.0.0   Tomcat Connector AJP
    8080 0.0.0.0   Tomcat Connector HTTP
    8443 0.0.0.0   Tomcat Connector HTTPS
    9999 0.0.0.0   JMX Remoting Connector
   61616 0.0.0.0   ActiveMQ Message Broker Connector

  Started Application Modules:
    EAR: geronimo/webconsole-tomcat/1.1/car
    RAR: geronimo/activemq/1.1/car
    RAR: geronimo/system-database/1.1/car
    WAR: geronimo/remote-deploy-tomcat/1.1/car
    WAR: geronimo/welcome-tomcat/1.1/car

  Web Applications:
    http://hcunico:8080/
    http://hcunico:8080/console
    http://hcunico:8080/console-standard
    http://hcunico:8080/remote-deploy

Geronimo Application Server started

Back to Top

shutdown

If the startup command starts the Apache Geronimo server, shutdown will definitively stop it. This command has the following syntax:

<geronimo_home>/bin/shutdown [options]

The available options are:

--user [user_name]
Specifies the user name with the authority to stop the server. By default you would normally use system as the user name.

--password [password]
Specifies the password for the user name you just entered. By default you would normally use manager as the password.

--port [port_number]
Specifies the RMI naming port to connect to the server (for example JMX connection port). By default you would normally use port 1099.

If you do not specify any parameters, this command will prompt you for a user name and password and will assume port 1099 by default and will not prompt for any port.

Back to Top

geronimo

The geronimo command lets you perform the previous two actions, that is start and stop the server in different modes depending on the parameters you specify. This command has the following syntax:

<geronimo_home>/bin/geronimo [options]

The available options are:

debug
This option will start the server in JDB debugger.

jpda run
This option will start the server in foreground under JPDA debugger

jpda start
This option will start the server in background under JPDA debugger.

run
This option will start the server in the current window.

start
This option will start the server in a separate window just like the startup command.

stop
This option will stop the server.

Both start and stop options for this command will have the same set of parameters as the startup and shutdown commands.

Back to Top

deploy

The deployer tool is used for installing, uninstalling, reinstalling, starting and stopping applications and modules and for installing and uninstalling configurations (for example some configuration specific deployment plans, security realms, database connection pools, etc.). Due to the number of options in this case, this tool is covered in detail in the Deployer tool section.

This is a powerful tool with many parameters and options but it is not hard to use at all.

As with the startup command, the deployment tool can also be invoked in two different ways:

java -jar deployer.jar [general_options] <command> [command_options]

or simply

deploy [general_options] <command> [command_options]

Please refer to Deployer tool for a fully detailed description of this tool options and usage.

Back to Top

client.jar

The client.jar launches the client application container. This command has the following syntax:

java -jar client.jar config-name [app arg] [app arg] ...

The first argument identifies the Geronimo configuration that contains the application client you want to run. The rest of the arguments will be passed as arguments to the client application when it is started.

Back to Top

upgrade.jar

This tools helps you to migrate deployment plans from Apache Geronimo v1.0, refer to Migrating applications from Geronimo v1.0 for details.

Back to Top