Custom server assemblies using Geronimo Administrative console has been edited by Ashish Jain (Jul 02, 2008).

(View changes)


This application will illustrate on assembling a customer server in Geronimo.

We are using Apache Geronimo V2.1.1 for this tutorial.
We have used an existing tutorial from tutorial section. Refer Stateless Session Bean tutorial for application development and deployment. Later we will assemble a custom server which will only include functional components required by our application.


Application client referred in this tutorial is actually a Web Application Client.

Identifying the functional components required by our server.

This is the major work required for our custom server which has been simplified by geronimo administrative console.

  1. To assemble a server from existing instance of geronimo we need to include geronimo-boilerplate-minimal plugin which includes several files used to start the server.
  2. To identify the various dependencies associated with our application Launch the Dependency Viewer under Debug Views.

  3. Expand EJBModule followed by default/StatelessSessionEJB/1.0/car. Select dependencies to list the dependencies for this application. Similarly expand WebModule followed by default/ApplicationClient/1.0/car and ResourceAdapterModule followed by console.dbpool/jdbc%2Fuserds/1.0/rar.

    Once done we have all the functional component required by our server.

Assembling a custom server.

  1. Launch the administrative console and select Plugins under Applications.

  2. Select Assemble a server.

  3. Name the artifacts as suggested in the figure.

  4. Next step is to select the plugins required in our custom server assembly. Select geronimo-boilerplate-minimal, WAR, EJB and there respective dependencies. You also have to select org.apache.geronimo.configs/derby/2.1.1/car since our application uses derby database.
  5. To get a web based administrative console you need to select org.apache.geronimo.plugins/console-tomcat/2.1.1/car. For the database wizard select org.apache.geronimo.plugins/sysdb-console-tomcat/2.1.1/car.
  6. Final list of plugins we have selected are as follows
    • org.apache.geronimo.assemblies/geronimo-boilerplate-minimal/2.1.1/jar
    • org.apache.geronimo.configs/axis/2.1.1/car
    • org.apache.geronimo.configs/axis2/2.1.1/car
    • org.apache.geronimo.configs/j2ee-server/2.1.1/car
    • org.apache.geronimo.configs/j2ee-corba-yoko/2.1.1/car
    • org.apache.geronimo.configs/jasper/2.1.1/car
    • org.apache.geronimo.configs/openejb/2.1.1/car
    • org.apache.geronimo.configs/openjpa/2.1.1/car
    • org.apache.geronimo.plugins/sysdb-console-tomcat/2.1.1/car
    • org.apache.geronimo.configs/system-database/2.1.1/car
    • org.apache.geronimo.configs/tomcat6/2.1.1/car
    • default/StatelessSessionEJB/1.0/car
    • default/ApplicationClient/1.0/car
    • org.apache.geronimo.configs/derby/2.1.1/car
    • org.apache.geronimo.plugins/console-tomcat/2.1.1/car
    • org.apache.geronimo.plugins/sysdb-console-tomcat/2.1.1/car

  7. Once done select Assemble.

  8. On the next screen each artifact and its associated properties will be displayed. Select Install.

  9. Once done you will receive a confirmation message suggesting the success or failure of server assembly. It will also enlist the location of the custom server assembly which by default is <GERONIMO_HOME>/var/temp/assembly.
  10. The server will be named as Unzip it and start the server.
  11. Since our Stateless Session Bean uses userdbs you need to create database and created table.
    This completes our illustration for custome server assembly

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences