This tutorial illustrates how to assemble a custom server by using an application-centric approach from console. By using this approach, our application will define the contents of the server. Custom server will be built around our application and will include only the components required by our application. You can use an existing tutorial from the tutorial section to develop a sample application. See the Stateless Session Bean tutorial for application development and deployment. This topic will assemble a custom server which will only include functional components required by the application.
Identifying the functional components required by our server
To use an application-centric approach, you need to find out the various dependencies required by your application. This is the major work required for assembling a custom server, which has been simplified by the Geronimo administration console.
- To assemble a server from existing instance of Geronimo, you need to include the Geronimo Plugin Group :: Framework plugin group, which is the framework of a functional server and pre-selected by default . See the Plugin Group section for more information about Geronimo Plugin Group :: Framework.
- To identify the application plugins to be included, find out the various dependencies required by your application. For example, for the sample application developed from the Stateless Session Bean tutorial, include the following plugins:
- Web archive plugin default/ApplicationClient/1.0/car
- StatelessSessionEJB plugin default/StatelessSessionEJB/1.0/car
- Datasource pool plugin console/dbpool/jdbc_userds/1.0/car
For information about how to get these plugins, See Converting applications into plugins using the Administration Console.
- To create a new database from the administration console, you need to include the plugin group Geronimo Plugins, Console :: System Database(Tomcat), which includes console interface plugin, embeded Derby database plugin, and required resource adapter plugins.
This completes the identification of all the functional component(dependencies) required by our application centric custom server.
Assembling a custom server
- Launch the administration console and select Plugins under Applications.
- Select Application Centric as the Custom Assembly Mode and then click Assemble a server.
- Name the artifacts as suggested: groupId as test, artifactId as TestServer and format as zip or so.
- The next step is to select the functional components that you identified. Select Geronimo Plugin Group :: Framework, WAR, EJB and database pool plugins. You also have to select Geronimo Plugins, Console :: System Database(Tomcat) because our application uses derby database and you have to create the database from console. Because application WAR, EJB and database pool plugins are dependent with each other, you are free to choose just one of them and therefore the rest of its dependencies will be assembled automatically.
You can also choose the Expert mode to select individual plugins instead of plugin groups.
- The final list of plugins/plugin groups you select should be follows:
- After this is done, click Assemble.
- On the next screen, each artifact and its associated properties will be displayed. Click Install.
- After this is done, you will receive a confirmation message suggesting the success or failure of the server assembly. It will also enlist the location of the custom server assembly, which by default is <GERONIMO_HOME>/var/temp/assembly.
- The server will be named as
TestServer-1.0-bin.zip. In the
<GERONIMO_HOME>/var/tempdirectory, you will find the package of the newly assembled server with minimizing footprint and the fewest components you need. Unzip it and start the server.
- Since our Stateless Session Bean uses userdbs, you need to create database and tables as suggested in the tutorial.
This completes our illustration for custom server assembly.