geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Geronimo Wiki] Update of "Deployment" by JacekLaskowski
Date Sun, 12 Jun 2005 20:38:33 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Geronimo Wiki" for change notification.

The following page has been changed by JacekLaskowski:

The comment on the change is:
Some hints for troubleshooters

  java -jar bin/deployer.jar distribute my-web-app.war geronimo-jetty.xml
  java -jar bin/deployer.jar distribute my-service-plan.xml
+   '''NOTE:''' Deployer will try to connect to a running Geronimo instance before starting
up its own itself. It's important when you encounter any weird error messages during deployment
and will be tearing your hair out over what might be wrong. It can be that the deployer has
connected to a defunct server or a server without Deployer running.
    '''NOTE:''' Though you can deploy while the server is running, that still only works if
you're on the same machine as the server.  Deployment to remote machines will come.
@@ -298, +300 @@

  You can "undeploy" by hacking around in the target/config-store directory.  The contents
appears to be a  properties file called, and a set of subdirectories with
numeric names.  The properties key is the configuration name and the value is the numeric
name of the subdirectory that contains that configuration.  So to "undeploy" a configuration
you just remove its entry from and delete its directory.
+ = Low-level details =
+ When the deployer is invoked, [*checkout*/geronimo/trunk/modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/
org.apache.geronimo.deployment.cli.DeployTool] of the deploy-tool module is executed. Take
a look at the class when in a urgent need to figure out how Geronimo deployment goes.

View raw message