Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

There are several alternatives available for installing and removing applications:

...

Geronimo Administration Console AnchorGACGAC

To install a new application via the Geronimo Administration Console the Install New Applications portlet is available by selecting Deploy New on the Console Navigation menu on the left hand side. This portlet also allows you to start automatically the application right after it was deployed.

...

Note that when specifying the deployment plan externally you can use any file name to identify that plan, there is no need to use the geronimo-XYZ.xml form. In our example we do not need to specify any additional deployment plans as we have the Geroniom Geronimo specific ones already included in the package.

Once deployed you should see a confirmation message similar to this one:noformat

bgColor#000000borderStylesolid D:\geronimo-tomcat6-jee5-2.0-M2\bin>deploy --user system --password manager deploy \HelloWorld_2.0\HelloWorld.war Using GERONIMO_BASE: D:\geronimo-tomcat6-jee5-2.0-M2 Using GERONIMO_HOME: D:\geronimo-tomcat6-jee5-2.0-M2 Using GERONIMO_TMPDIR: D:\geronimo-tomcat6-jee5-2.0-M2\var\temp Using JRE_HOME: C:\Java\jdk1.5.0_06\\jre Deployed sample.applications/HelloWorldApp/2.0/war @ http://hcunico:8080/hello

As a difference from the deployment via de the Geronimo Administration Console, using the command line tool you receive more information in the confirmation message. For instance you receive the Component Name (a.k.a. moduleId) and you also receive the context root and port where the application was deployed. This is very useful when installing, testing and uninstalling several different applications where it would be hard to remember all these values.

...

You will receive a list similar as the one shown in the following example. No FormatbgColor

#000000borderStylesolid D:\geronimo-tomcat6-jee5-2.0-M2\bin>deploy --user system --password manager list-modules Using GERONIMO_BASE: D:\geronimo-tomcat6-jee5-2.0-M2 Using GERONIMO_HOME: D:\geronimo-tomcat6-jee5-2.0-M2 Using GERONIMO_TMPDIR: D:\geronimo-tomcat6-jee5-2.0-M2\var\temp Using JRE_HOME: C:\Java\jdk1.5.0_06\\jre Found 47 modules + console.dbpool/LocalDB/1.0/rar + console.dbpool/jdbc%2FTradeDataSource/1.0/rar + org.apache.geronimo.configs/activemq/2.0-M2/car + org.apache.geronimo.configs/activemq-broker/2.0-M2/car + org.apache.geronimo.configs/axis/2.0-M2/car + org.apache.geronimo.configs/axis-deployer/2.0-M2/car + org.apache.geronimo.configs/axis2/2.0-M2/car + org.apache.geronimo.configs/axis2-deployer/2.0-M2/car + org.apache.geronimo.configs/client-deployer/2.0-M2/car + org.apache.geronimo.configs/connector-deployer/2.0-M2/car + org.apache.geronimo.configs/cxf/2.0-M2/car + org.apache.geronimo.configs/cxf-deployer/2.0-M2/car + org.apache.geronimo.configs/dojo-tomcat/2.0-M2/car @ http://hcunico:8080/dojo + org.apache.geronimo.configs/geronimo-gbean-deployer/2.0-M2/car + org.apache.geronimo.configs/hot-deployer/2.0-M2/car + org.apache.geronimo.configs/j2ee-deployer/2.0-M2/car + org.apache.geronimo.configs/j2ee-security/2.0-M2/car + org.apache.geronimo.configs/j2ee-server/2.0-M2/car + org.apache.geronimo.configs/j2ee-system/2.0-M2/car + org.apache.geronimo.configs/javamail/2.0-M2/car + org.apache.geronimo.configs/jee-specs/2.0-M2/car + org.apache.geronimo.configs/openejb/2.0-M2/car + org.apache.geronimo.configs/openejb-deployer/2.0-M2/car + org.apache.geronimo.configs/persistence-jpa10-deployer/2.0-M2/car + org.apache.geronimo.configs/remote-deploy-tomcat/2.0-M2/car @ http://hcunico:8080/remote-deploy + org.apache.geronimo.configs/rmi-naming/2.0-M2/car + org.apache.geronimo.configs/sharedlib/2.0-M2/car + org.apache.geronimo.configs/system-database/2.0-M2/car + org.apache.geronimo.configs/tomcat6/2.0-M2/car + org.apache.geronimo.configs/tomcat6-deployer/2.0-M2/car + org.apache.geronimo.configs/transaction-jta11/2.0-M2/car + org.apache.geronimo.configs/webconsole-tomcat/2.0-M2/car `-> standard.war @ http://hcunico:8080/console-standard `-> framework.war @ http://hcunico:8080/console + org.apache.geronimo.configs/webservices-common/2.0-M2/car + org.apache.geronimo.configs/welcome-tomcat/2.0-M2/car @ http://hcunico:8080/ + sample.applications/HelloWorldApp/2.0/war @ http://hcunico:8080/hello org.apache.geronimo.configs/ca-helper-tomcat/2.0-M2/car org.apache.geronimo.configs/client/2.0-M2/car org.apache.geronimo.configs/client-security/2.0-M2/car org.apache.geronimo.configs/client-system/2.0-M2/car org.apache.geronimo.configs/client-transaction/2.0-M2/car org.apache.geronimo.configs/directory/2.0-M2/car org.apache.geronimo.configs/ldap-realm/2.0-M2/car org.apache.geronimo.configs/online-deployer/2.0-M2/car org.apache.geronimo.configs/openjpa/2.0-M2/car org.apache.geronimo.configs/shutdown/2.0-M2/car org.apache.geronimo.configs/transformer-agent/2.0-M2/car org.apache.geronimo.configs/uddi-tomcat/2.0-M2/car

Look for the sample.applications/HelloWorldApp/2.0/war entry, thas that is the value you will have to use when trying to uninstall the application.

To uninstall the application run the following command from the <geronimo_home>\bin diretory directory using the Component Name you identified while listing the modules.

...

This command will first stop the runnning running application and then uninstall it. You should see a confirmation message similar to this: No FormatbgColor

#000000borderStylesolid D:\geronimo-tomcat6-jee5-2.0-M2\bin>deploy --user system --password manager undeploy sample.applications/HelloWorldApp/2.0/war Using GERONIMO_BASE: D:\geronimo-tomcat6-jee5-2.0-M2 Using GERONIMO_HOME: D:\geronimo-tomcat6-jee5-2.0-M2 Using GERONIMO_TMPDIR: D:\geronimo-tomcat6-jee5-2.0-M2\var\temp Using JRE_HOME: C:\Java\jdk1.5.0_06\\jre Module sample.applications/HelloWorldApp/2.0/war unloaded. Module sample.applications/HelloWorldApp/2.0/war uninstalled. Undeployed sample.applications/HelloWorldApp/2.0/war

In this example you have used the same tool with three different commands:

...

These are not the only options and commands available for this tool, please visit the Tools and commands section for additional details.

Hot deployment

Apache Geronimo has support for Hot Deployment. This means that you can copy an application JAR file into the <geronimo_home>/deploy directory and the application will be deployed automatically. This will also work for uninstalling or refreshing applications previously deployed via this method. Alternatively, you may also copy the directory (unpacked) for the application module instead of copying a single JAR file.

Note that with this deployment method you have to include the deployment plan in the application package, this method does not support external deployment plans. Also note that applications deployed via the Deployer tool or the Geronimo Administration Console will not be listed in the <geronimo_home>/deploy directory.

When you copy an application in the deploy directory, let's say HelloWorld.war, you will see a confirmation message in the console where Geronimo is running stating the application was deployed and the context to access that application.

#000000solid 11:45:23,500 INFO [DirectoryHotDeployer] Deploying HelloWorld.war 11:45:23,953 INFO [DirectoryHotDeployer] Deployed sample.applications/HelloWorldApp/2.0/war @ http://hcunico:8080/hello

To remove the application, just delete the WAR or EAR file from the deploy directory. When the application has been removed you should see a confirmation message in the console where Geronimo is running stating the application was undeployed.

#000000solid 11:46:17,953 INFO [DirectoryHotDeployer] Undeploying HelloWorld.war 11:46:18,281 INFO [DirectoryMonitor] Hot deployer notified that an artifact was removed: sample.applications/HelloWorldApp/2.0/war 11:46:18,281 INFO [DirectoryHotDeployer] Undeployed sample.applications/HelloWorldApp/2.0/war

Summary

In this section we has discussed three different methods for installing and uninstalling applications, one graphical, one command line and for the hot deployment you can choose command line or the GUI of your choice.
Visit the Tools and commands section for further details on the available options and parameters.