Wiki Markup |
---|
{scrollbar} |
Wiki Markup |
---|
{composition-setup}{composition-setup} |
Excerpt |
---|
GShell is an extensible, command-line processing environment for creating command-line applications |
...
This document is organized in the following sections:
Children Display | ||
---|---|---|
|
Connecting to an Already Running Geronimo Instance
deploy/connect
can be used to connect to an instance of Geronimo that is already running. If no options are provided, then the default port (1099) and host (localhost) will be used to connect to a server. The -p
option can be used to specify a different port and -s
to specify a remote hostname.
No Format bgColor #000000 borderStyle solid
jason@Jason-Warners-Computer.local:/> deploy/connect --port 1099 --hostname foo.bar.com
Connecting to Geronimo server: foo.bar.com:1099
Username: system
Password: *******
Note | ||
---|---|---|
| ||
When issuing a |
deploy/disconnect
can be used to disconnect from an already connected instance of Geronimo. Since only one instance of Geronimo can be connected at a time, no options are needed to specify which server to disconnect from.
No Format bgColor #000000 borderStyle solid
jason@Jason-Warners-Computer.local:/> deploy/disconnect
Disconnecting from Geronimo server
Connection ended
Deploying an Application to a Server Instance
Deploy
deploy/deploy
can be used to deploy a module to the geronimo instance that is currently connected.
A module file can be one of the following:
- J2EE Enterprise Application Archive (EAR) file
- J2EE Web Application Archive (WAR) file
- J2EE Enterprise JavaBean Archive (JAR) file
- J2EE Java Resource Archive (RAR) file
No Format bgColor #000000 borderStyle solid
jason@butters:/> deploy/deploy <module>
Connecting to Geronimo server: localhost:1099
Username: system
Password: *******
The -u
and -w
options can be used to provide username and password when issuing the command. The -s
option can be used to specify the hostname. If none specified, then the hostname defaults to localhost. Likewise -p
can be used to specify a port to contact the host on with 1099 being the default. -i
can be used to specify an inPlace deployment from the directory you are actually developing the application. In that instance, the path to the application would need to be provided in place of the location of the module.
A deployment plan is necessary to deploy an application. If the deployment plan is not in the WEB-INF directory of a module, then its location must be specified after the module in the command.
No Format bgColor #000000 borderStyle solid
jason@butters:/> deploy/deploy <module> <deployment plan>
Redeploy
deploy/redeploy
is used to deploy a newer version of a module onto a server where the older module is already deployed. It functions in a similar way to deploy/deploy
but lacks an inPlace deployment option. The username and password is still required and can be provided via command line (-u
and -w
) or through a prompt after the command is issued. As with the deploy command, the user can specify both port (-p)
and hostname (-s)
if they differ from the defaults
No Format bgColor #000000 borderStyle solid
jason@butters:/> deploy/redeploy -u system -w manager <module>
Undeploy
deploy/undeploy
is used to properly remove a module from a server. The command takes the username (-u)
and password (-w)
options. If not provided, the user will be prompted. As with the deploy command, the user can specify both port (-p)
and hostname (-s)
if they differ from the defaults. The module id must be provided for the module you wish to undeploy.
No Format bgColor #000000 borderStyle solid
jason@butters:/> deploy/undeploy -u system -w manager <module_id>
Distribute
deploy/distribute
works exactly like deploy/deploy
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. The command can be issued in the same way, with the same options, as deploy/deploy
.
...
bgColor | #000000 |
---|---|
borderStyle | solid |
...
|