The Geronimo Deployment Architecture


As you venture to creation of your own deployment plans for your application modules, it is very helpful to keep the Geronimo deployment architecture in mind. As an administrator, you will need to know how deployed modules are managed by Geronimo and how module IDs are assigned by default.

Deployed Module in the Repository

Figure 9-2 illustrates how the information associated with a deployed module is stored in the repository in Geronimo.

image from book
Figure 9-2: Deployed modules stored in the repository

In Figure 9-2, you can see that a module deployed into the Geronimo server has the following properties:

  • Its binaries, as well as configuration information, are stored in the repository as artifacts.

  • It is assigned a module ID.

  • All subsequent operations with the module, once deployed, are always via the module ID.

The Geronimo server deals in configuration management. This is, as the name implies, the management of configured modules (grouping of GBeans). As such, the configuration of a module being deployed into the server is turned into a serialized module configuration, and configurations are stored in the repository (see Chapter 6 for more information on how these serialized module configuration files are stored there).

Assignment of Module IDs

The main method of controlling the actual module ID that is used by Geronimo is via the <moduleId> element in the various Geronimo-specific deployment plans. For example, in the geronimo-web.xml deployment plan, the module ID may be declared as follows:

  <?xml version="1.0" encoding="UTF-8"?> <web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.1"> <environment xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">     <moduleId>       <groupId>com/wrox/progeronimo</groupId>       <artifactId>progeron</artifactId>       <version>1.0</version>       <type>car</type>     </moduleId>   </environment> 

The highlighted lines in the preceding listing specifies that the module ID for this deployed WAR file should be, in short form: com/wrox/progeronimo/progeron/1.0/car.

If you do not specify the optional modueId in the <environment> element in your Geronimo-specific deployment plan, Geronimo’s deployment code will try its best to create one for you. It will assign the following default moduleId:

 <default group>/<basename of your deployed module>/<timestamp>/car

The <default group> for Geronimo 1.1 is default. The base name of your deploy module is the filename without the file extension. For example, the base name for progeron.war is progeron, and for authors.ear is authors. The <timestamp> element, created to stand in as a default version number, reflects the time of deployment expressed as a long integer (64-bit number).




Professional Apache Geronimo
Professional Apache Geronimo (Wrox Professional Guides)
ISBN: 0471785431
EAN: 2147483647
Year: 2004
Pages: 148

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net