 | Not completed yet |
The gogo commands for Geronimo is an extension of Apache karaf Shell to interact with Geronimo kernel. Those command names are made up of two parts: <scope>:<name> by convention as listed below. Click each command to learn about its usage.
To enter the karaf shell, press Enter after you start up the Geronimo server using geronimo run command.
Note that if the <name> portion of the command is unique, then you only need to type it. If not, then you must either type the full <scope>:<name> or arrange the scope search path accordingly. For example, you can use list-modules instead of deploy:list-modules to list all modules in the server repository.
Following options are common to those commands:
generaloptions includes:
-s or --server, --hostname
Hostname, default localhost
Specify an Username to start the server
Specify the password to start the server
Display this help message
geronimo:start-server
The server can be started through Felix Shell using the geronimo:start-server command. It uses the following syntax:
start-server generaloptions commandoptions
where
commandoptions includes:
Use a specific Java Agent, set to none to disable
Run the server process in the background
Define Geronimo system properties
Use a specific Geronimo home directory
Use a specific Java Virtual Machine for server process
Set a Java Virtual Machine flag
Capture console output to a specified log file
Start up a specific module by name
Specify a configuration profile
Suppress informative and warning messages
Specify the timeout for the server process in seconds
Enable verbose output; specify multiple times to increase verbosity
start-server command examples
Back to Top
geronimo:stop-server
The server can be stopped using the geronimo/stop-server command. It uses the following syntax:
stop-server generaloptions commandoptions
Where
commandoptions includes:
stop-server command examples
Use this syntax to stop the server.
geronimo> geronimo:stop-server --hostname localhost -p 1099
Back to Top
geronimo:wait-for-server
The command is used to verify if the server has started in the given time (in seconds). It uses the following syntax:
wait-for-server generaloptions commandoptions
Where
commandoptions includes:
Specify the time (in seconds) to wait while verifying the that the server has started. 60 seconds by default
wait-for-server command examples
Back to Top
deploy:login
The command is used to save the username and password for the current connection to a file to avoid future prompting. This command is used for remote connections. Local connections, by default, affect in the embeded mode which does not support this function. It has the following syntax:
login generaloptions commandoptions
where
commandoptions includes:
login command examples
Back to Top
deploy:encrypt
The command is used to generates an encrypted string using org.apache.geronimo.util.EncryptionManager. It has the following syntax:
encrypt commandoptions string
where
commandoptions includes:
string is a string to be encrypted
encrypt command examples
Use this syntax to encrypt string passw0rd on an active server so that the encryption settings of that server will be used.
geronimo> deploy:encrypt passw0rd
Online encryption result is shown below:
String to encrypt: passw0rd
Online encryption result:
{Simple}rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNv
ZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNBbGd0ABJMamF2YS9s
YW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHB1cgACW0Ks8xf4BghU4AIAAHhwAAAAEG2NoqXONCcU
GqfK0reVCpVwdAADQUVT
Back to Top
deploy:assemble-server
The command is used to extract a customized server assembly from the current one. It has the following syntax:
assemble-server generaloptions commandoptions
Where
commandoptions includes:
Specify the server artifact name
Specify if the assembly is in .zip or tar.gz format
Specify the group ID of the library
Specify the assembly location, where your specific plug-ins are stored. The default location is <geronimo_home>/var/temp/
assemble-server command examples
Use this syntax to create a custom server assembly, which is placed at <geronimo_home>/var/temp/.
geronimo> deploy:assemble-server -f zip -g group1 -a assemble1
Back to Top
geronimo:start-client
The command is used to start a Geronimo application client. Note that before starting a client, you have to deploy the application to the server. It has the following syntax:
start-client generaloptions commandoptions
Where
commandoptions includes:
Use a specific Java Agent, set to none to disable
Run the server process in the background
Define Geronimo system properties
Use a specific Geronimo home directory
Use a specific Java Virtual Machine for server process
Set a Java Virtual Machine flag
Capture console output to a specified log file
Specify a configuration profile
Specify the timeout for the server process in seconds
Enable verbose output; specify multiple times to increase verbosity
start-client command examples
Back to Top
deploy:connect
The command is used to connect to an instance of Geronimo that is already running. After connected successfully, you can run a series of commands on the remote server. It has the following syntax:
connect generaloptions commandoptions
Where
commandoptions includes:
connect command examples
Back to Top
deploy:disconnect
The command is used to close the connection to a remote Geronimo server. Only one instance of the server can be connected at a time, no additional options are needed to specify which server to disconnect from. If you are trying to connect to a second server instance, use this command to disconnect first. It has the following syntax:
disconnect command examples
Back to Top
deploy:deploy-module
The command is used to deploy a module to a Geronimo server. Once deployed, a module is identified by its module ID within Geronimo. It has the following syntax:
deploy-module generaloptions commandoptions <module> <deployment plan>
where
module is a module file, which is required for the command and can be one of the following:
- Java EE Enterprise Application Archive (EAR) file
- Java EE Web Application Archive (WAR) file
- Java EE Enterprise JavaBean Archive (JAR) file
- Java EE Java Resource Archive (RAR) file
- Web Archive Bundle(WAB) file
- Enterprise Bundle Archive(EBA) file
deployment plan is an optional plan file for Java EE module. If the deployment plan for a Java EE archive file is not in the WEB-INF directory, its location must be specified after the module in the command. See Understanding deployment plans for more details.
commandoptions includes:
Add and start an archive or directory to an active server, without the archive or directory being copied into the server directory tree
Specify the target repository to be deployed into. See list-targets for the names of repositories available on the server.
deploy-module command examples
Use this syntax to deploy a WAR file.
deploy-module d:/HelloWorld.war
Use this syntax to deploy a WAR file whose deployment plan is located outside of the WEB-INF directory.
geronimo> deploy:deploy-module d:/HelloWorld.war d:/geronimo-web.xml
Back to Top
deploy:distribute-module
The command works exactly like deploy-modules except the module is not started once it has been deployed into the server and is not marked to be started each time the server starts. It has the same syntax and options as deploy-modules:
distribute-module generaloptions commandoptions <module> <deployment plan>
distribute command examples
Use this syntax to distribute a module whose deployment plan is located outside of the WEB-INF directory.
geronimo> deploy:distribute-module d:/HelloWorld.war d:/geronimo-web.xml
Back to Top
deploy:list-targets
The command is used to list all available target repositories on the server. It has the following syntax:
list-targets generaloptions commandoptions
where
commandoptions includes:
list-targets command examples
Back to Top
deploy:list-plugins
The command is used to list all of plugins in a certain maven repository. It has the following syntax:
list-plugins generaloptions commandoptions
where
commandoptions includes:
-rr or --refresh-repository
list-plugins command examples
Use this syntax to first access the list of repositories. Select a repository from the list, plugins in this repository is displayed.
Use this syntax to display the list of plugins in the given repository using secure channel.
Back to Top
deploy:new-server-instance
The command is used to create a new server instance. It has the following syntax:
new-server-instance generaloptions commandoptions instancename
where
commandoptions includes:
instancename is the name of the new instance.
new-server-instance command examples
Use this syntax to create a new server instance.
geronimo> deploy:new-server-instance instance2
Back to Top
deploy:redeploy-module
The command is used to deploy a newer version of a module onto a server where the older module is already deployed. It has the following syntax:
redeploy-module generaloptions commandoptions <module> <deployment plan> <module id>
where
module is a module file, which is required for the command and can be one of the following:
- Java EE Enterprise Application Archive (EAR) file
- Java EE Web Application Archive (WAR) file
- Java EE Enterprise JavaBean Archive (JAR) file
- Java EE Java Resource Archive (RAR) file
- Web Archive Bundle(WAB) file
deployment plan is an optional plan file for Java EE module. If the deployment plan for a Java EE archive file is not in the WEB-INF directory, its location must be specified after the module in the command. See Understanding deployment plans for more details.
module id is the configuration on the server you want to replace. If you do not specify the module_id, the plan supplied (or plan inside the module) will be used to determine the actual configuration that you wish to redeploy. Redeploying a plan with an existing module ID allows you to modify the configuration of a running module without intermediate undeployment.
commandoptions includes:
redeploy-module command examples
Use this syntax to deploy a newer version of an existing module .
geronimo> deploy:redeploy-module D:/HelloWorld.war default/HelloWorld/1.0/car
Back to Top
deploy:undeploy-module
The command is used to properly remove a module from a server. It has the following syntax:
undeploy-module generaloptions commandoptions <module id>
where
module id is the configuration name you want to remove from the server. It must be provided.
commandoptions includes:
undeploy-module command examples
Use this syntax to remove an existing module.
geronimo> deploy:undeploy-module default/HelloWorld/1.0/car
Back to Top
deploy:start-module
The command is used to start an existing module on the server which is not running. It use the following syntax:
start-module generaloptions commandoptions <module id>
where
module id is the configuration name you want to start on the server. It must be provided.
commandoptions includes:
start-module command examples
Use this syntax to start an existing module.
geronimo> deploy:start-module default/HelloWorld/1.0/car
Back to Top
deploy:stop-module
The command is used to stop a running module on the server. It use the following syntax:
start-module generaloptions commandoptions <module id>
where
module id is the configuration name you want to stop on the server. It must be provided.
commandoptions includes:
stop-module command examples
Use this syntax to stop a running module.
geronimo> deploy:stop-module default/HelloWorld/1.0/car
Back to Top
deploy:restart-module
The command is used to restart a module on the server. It has the following syntax:
restart-module generaloptions commandoptions <module id>
where
module id is the configuration name you want to restart on the server. It must be provided.
commandoptions includes:
restart-module command examples
Use this syntax to restart a module.
geronimo> deploy:restart-module default/HelloWorld/1.0/car
Back to Top
deploy:list-modules
The command is used to list modules in the target repository. It has the following syntax:
list-modules generaloptions commandoptions <targetname>
where
commandoptions includes:
Show stopped modules only
Show started modules only
Show started and stopp modules only, this one is default if you did not specify any parameters
targetname is the name of target repository. See list-targets for more details.
list-modules command exmaples
Use this syntax to list the started modules in the target repository.
geronimo> deploy:list-modules -r
Back to Top
deploy:install-plugin
The command is used to install a geronimo plugin into the server. It has the following syntax:
install-plugin generaloptions commandoptions <configuration archive>
where
commandoptions includes:
configuration archive is the fully qualified name of plugin archive. The archive must be a valid Geronimo plugin file.
install-plugin command examples
Use this syntax to deploy a CAR file.
geronimo> deploy:install-plugin d:/HelloWorld-1.0.car
Back to Top
deploy:install-library
The command is used to install a geronimo library into the server. It has the following syntax:
install-library generaloptions commandoptions <configuration archive>
where
commandoptions includes:
Specify the group ID of the library
configuration archive is the fully qualified name of library archive.
If installed successfully, the library will be found in <geronimo_home>/repository
install-library command examples
Use this syntax to install a geronimo library.
geronimo> deploy:install-library d:/temp/openejb-ejbd-3.2-SNAPSHOT.jar
Back to Top
deploy:unlock-keystore
The command is used to unlock a keystore and private key in Geronimo server. It has the following syntax:
unlock-keystore generaloptions commandoptions <keystore>
where
commandoptions includes:
keystore is the name of keystore or private key you want to unlock.
unlock-keystore command examples
Back to Top
equinox:diagnose
The command is used to diagnose constraints of an installed OSGi bundle and verify if the bundle can be resolved successfully. The command is only available in Equinox OSGi runtime.
diagnose generaloptions <bundleIDs>
where
bundleIDs is a list of bundle IDs seperated by whitepaces.
diagnose command examples
Use this syntax to diagnose the resolver problem of a bundle with Id 85.
geronimo> diagnose 85
mvn:org.apache.geronimo.framework/geronimo-service-builder/3.0-SNAPSHOT 85
No unresolved constraints.
Back to Top