THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
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.5.0_06)...
17:56:58,656 INFO [root] ----------------------------------------------
17:56:58,656 INFO [root] Started Logging Service
17:56:58,656 INFO [root] Runtime Information:
17:56:58,656 INFO [root] Install Directory = D:\geronimo-tomcat-j2ee-1.2
17:56:58,656 INFO [root] JVM in use = Sun Microsystems Inc. Java 1.5.0_06
17:56:58,656 INFO [root] Java Information:
17:56:58,656 INFO [root] System property [java.runtime.name] = Java(TM) 2 Runtime Environment, Standard Edition
17:56:58,656 INFO [root] System property [java.runtime.version] = 1.5.0_06-b05
17:56:58,656 INFO [root] System property [os.name] = Windows XP
17:56:58,656 INFO [root] System property [os.version] = 5.1
17:56:58,656 INFO [root] System property [sun.os.patch.level] = Service Pack 2
17:56:58,656 INFO [root] System property [os.arch] = x86
17:56:58,656 INFO [root] System property [java.class.version] = 49.0
17:56:58,656 INFO [root] System property [locale] = en_US
17:56:58,656 INFO [root] System property [unicode.encoding] = UnicodeLittle
17:56:58,656 INFO [root] System property [file.encoding] = Cp1252
17:56:58,656 INFO [root] System property [java.vm.name] = Java HotSpot(TM) Client VM
17:56:58,656 INFO [root] System property [java.vm.vendor] = Sun Microsystems Inc.
17:56:58,656 INFO [root] System property [java.vm.version] = 1.5.0_06-b05
17:56:58,656 INFO [root] System property [java.vm.info] = mixed mode
17:56:58,656 INFO [root] System property [java.home] = C:\Java\jdk1.5.0_06\jre
17:56:58,656 INFO [root] System property [java.classpath] = null
17:56:58,656 INFO [root] System property [java.library.path] = C:\Java\jdk1.5.0_06\jre\bin;....
17:56:58,656 INFO [root] System property [java.endorsed.dirs] = C:\Java\jdk1.5.0_06\\jre\lib\endorsed;D:\geronimo-tomcat-j2ee-1.2\lib\endorsed
17:56:58,671 INFO [root] System property [java.ext.dirs] = C:\Java\jdk1.5.0_06\\jre/lib/ext;D:\geronimo-tomcat-j2ee-1.2/lib/ext
17:56:58,671 INFO [root] System property [sun.boot.class.path] = D:\geronimo-tomcat-j2ee-1.2\lib\endorsed\xalan-2.7.0.jar;...
17:56:58,671 INFO [root] ----------------------------------------------
Module 1/25 org.apache.geronimo.configs/rmi-naming/1.2/car started in .297s
Module 2/25 org.apache.geronimo.configs/j2ee-server/1.2/car started in .156s
Module 3/25 org.apache.geronimo.configs/transaction/1.2/car started in .328s
Module 4/25 org.apache.geronimo.configs/j2ee-security/1.2/car started in .469s
Module 5/25 org.apache.geronimo.configs/axis/1.2/car started in .063s
Module 6/25 org.apache.geronimo.configs/openejb/1.2/car started in 2.938s
Module 7/25 org.apache.geronimo.configs/system-database/1.2/car started in .000s
Module 8/25 org.apache.geronimo.configs/activemq-broker/1.2/car started in 2.360s
Module 9/25 org.apache.geronimo.configs/activemq/1.2/car started in .391s
Module 10/25 org.apache.geronimo.configs/tomcat/1.2/car started in 1.782s
Module 11/25 org.apache.geronimo.configs/geronimo-gbean-deployer/1.2/car started in .281s
Module 12/25 org.apache.geronimo.configs/j2ee-deployer/1.2/car started in .250s
Module 13/25 org.apache.geronimo.configs/connector-deployer/1.2/car started in .156s
Module 14/25 org.apache.geronimo.configs/persistence-jpa10-deployer/1.2/car started in .032s
Module 15/25 org.apache.geronimo.configs/openejb-deployer/1.2/car started in .312s
Module 16/25 org.apache.geronimo.configs/client-deployer/1.2/car started in .079s
Module 17/25 org.apache.geronimo.configs/axis-deployer/1.2/car started in .906s
Module 18/25 org.apache.geronimo.configs/sharedlib/1.2/car started in .000s
Module 19/25 org.apache.geronimo.configs/tomcat-deployer/1.2/car started in .093s
Module 20/25 org.apache.geronimo.configs/welcome-tomcat/1.2/car started in .156s
Module 21/25 org.apache.geronimo.configs/webconsole-tomcat/1.2/car started in 1.563s
Module 22/25 org.apache.geronimo.configs/remote-deploy-tomcat/1.2/car started in .156s
Module 23/25 org.apache.geronimo.configs/hot-deployer/1.2/car started in 2.875s
Module 24/25 sample.applications/HelloWorldApp_1/1.2/war started in .063s
Module 25/25 sample.applications/HelloWorldApp_2/1.2/war started in .062s
Startup completed in 18 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 0.0.0.0 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
61613 0.0.0.0 ActiveMQ Transport Connector
61616 0.0.0.0 ActiveMQ Transport Connector
Started Application Modules:
EAR: org.apache.geronimo.configs/webconsole-tomcat/1.2/car
RAR: org.apache.geronimo.configs/activemq/1.2/car
RAR: org.apache.geronimo.configs/system-database/1.2/car
WAR: org.apache.geronimo.configs/dojo-tomcat/1.2/car
WAR: org.apache.geronimo.configs/remote-deploy-tomcat/1.2/car
WAR: org.apache.geronimo.configs/welcome-tomcat/1.2/car
WAR: sample.applications/HelloWorldApp_1/1.2/war
WAR: sample.applications/HelloWorldApp_2/1.2/war
Web Applications:
http://hcunico:8080/
http://hcunico:8080/console
http://hcunico:8080/console-standard
http://hcunico:8080/dojo
http://hcunico:8080/hello_1
http://hcunico:8080/hello_2
http://hcunico:8080/remote-deploy
Geronimo Application Server started
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.
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.
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 poolsm 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.
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.