Java™ Application Development on Linux - Dator

23.3 Deploying the EAR515automatic construction of various components by the server. It’s not as dauntingas it sounds—at least not any more.23.3.1 JBossOne of the great things about JBoss is its dynamic or “hot” deployment. Theonly work involved in deploying your application, if you have the EAR file builtproperly, is to copy the EAR file to the deployment directory. JBoss does allthe rest.Here is a listing of a very simple shell script that does what is needed, followedby an invocation of that shell script to install our BudgetPro exampleEAR file.$ cat ejbinstallcp $* /usr/local/jboss-3.2.3/server/default/deploy$ ejbinstall budgetpro.ear$Of course, this assumes that execute permission has been given to thescript and it is located in the search path. Furthermore, it assumes that JBoss(version 3.2.3) was installed in /usr/local.23.3.2 GeronimoGeronimo will be undergoing lots of change between the time that we writethis and the time that you read this. Be sure to check the Geronimo Web site 1for the latest information.Geronimo deployment is done as a separate executable step and is notfolded into the server. This separation of functions keeps the server smaller andquicker on startup. The deployer has the smarts for reading in all the XMLconfiguration information for your bean, building all the needed classes, andserializing it to package it up.To deploy our EAR, we execute the following command from theGeronimo home directory:$ java -jar bin/deployer.jar --install --module budgetpro.ear1. http://geronimo.apache.org/