Assembling a server via Console has been edited by Runhua Chi (Jan 03, 2009).

(View changes)


In the following section we will illustrate the steps on assembling a customer server in Geronimo. We are using Apache Geronimo V2.2 for this tutorial. In this tutorial we are taking an application centric approach. Using this approach our application will define on the contents of server. Custom server will be built around our application and will include only the components required by our application. For the application 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 step is required to identify the various dependencies required by our application. Since we are following an application centric approach we need to find out the various dependencies required by our application.
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 Plugin Group :: Framework plugin group which is the framework of a functional server. Refer plugins in Geronimo section for more information on Geronimo Plugin Group :: Framework.
  2. To identify the application plugins to be included, in this tutorial they are:
    1. Web archive plugin default/ApplicationClient/1.0/car
    2. StatelessSessionEJB plugin default/StatelessSessionEJB/1.0/car
      More information about how to get these plugins, please look into Converting applications into plugins using the Administrative Console.
  3. To create a new database, we need to include Geronimo Plugins, Console :: System Database.
  4. To use the admin console for database creation, we need to include Geronimo Plugins, ActiveMQ v5 :: Console
    This completes the identification of all the functional component(dependencies) required by our application centric custom 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 functional components we identified. Select Geronimo Plugin Group :: Framework, WAR and EJB plugins. You also have to select Geronimo Plugins, Console :: System Database since our application uses derby database.
  5. To get a web based administrative console you need to select Geronimo Plugins, ActiveMQ v5 :: Console.
    You can also choose the Expert mode to select indivial plugins instead of plugin groups.
  6. Final list of plugins/plugin groups we have selected are as follows
    • org.apache.geronimo.plugingroups/framework/2.2-SNAPSHOT/car
    • org.apache.geronimo.plugins/activemq-console-jetty/2.2-SNAPSHOT/car
    • org.apache.geronimo.configs/system-database/2.2-SNAPSHOT/car
    • default/StatelessSessionEJB/1.0/car
    • default/ApplicationClient/1.0/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 table as suggested in the tutorial.
    This completes our illustration for custom server assembly

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

Unsubscribe or edit your notifications preferences