Page History

...

java -jar deployer.jar <general_options> deploy <module> <deployment_plan>

The most common <general_options> would be --user and --password. New in this release is the --inPlace option that allows you to deploy an application without copying it (as part of the deployment process itself) to the Geronimo repository. In other words, you can have an application running in Geronimo but that application may be anywhere else on the file system.The <module> specifies the application file name and location. The <deployment_plan> specifies the file name and location of the XML with the deployment plan. Sometimes the application module already has included in the package a deployment plan or the application is so simple that does not require any deployment plan, in these cases this parameter can be omited.

...

If the server is not currently running at the time of deploying the application, the module will be marked to start next time the server is started.

The most common <general_options> would be --user and --password. The --inPlace option allows you point to and deploy an application directly from a directory external to Geornimo without the need for even packaging the application. In other words, you can have an application running in Geronimo but that application may be anywhere else on the file system.

To use this option you should type:

java -jar deployer.jar <general_options> deploy --inPlace <app_home>

Where <app_home> indicates the home directory where you have your application (exploded).

You can also deploy applications if Geronimo is not running by using the --offline option, the syntax for this command would be:

java -jar deployer.jar <general_options> --offline deploy <module>

Off course, you can also combine --offline and --inPlace

java -jar deployer.jar <general_options> --offline deploy --inPlace <app_home>

Back to top

Login

Anchor
login login

...

So, next time you run a different command that originally required user name and passowrdpassword, you can run the command directly, for example:

...

Where <moduleIDs> is a list of one or more modules (configID) separated by blank space. The module identification (or ConfigID) is defined at deployment time in the respective deployment plan for each module previously deployed.

This command has the same ability as with deploy to uninstall applications when the server is not running, this command has the following syntax:

java -jar deployer.jar <general_options> --offline undeploy <moduleID>

Back to top

Distribute

Anchor
distribute distribute

...

Use the list-modules command to list all available modules on the server, note that for running this command the server must be runnningrunning. The list-modules command has the following syntax:

...