|Home > Documentation > Developer's guide > Tutorials > Geronimo plugins > Custom server assemblies using Geronimo Administrative console|
Geronimo has always been a flexible, component-based server environment which allowed lightweight server images to be custom built for specific application environments – minimizing server footprint and reducing server startup time. Until now, creating customized Geronimo server runtimes was largely a build-time operation. Geronimo 2.1 greatly simplifies build-time customization, but also allows users to export a new custom server image from a running Geronimo server. Users may take a function-centric approach, choosing the desired set of server plugins for the server (e.g. Web Container+JMS+Deploy capabilities), or an application-centric approach, choosing one or more application plugins and allowing Geronimo to calculate the necessary server components required by the applications.
In the following section we will illustrate the steps on assembling a customer server in Geronimo. We are using Apache Geronimo V2.1.1 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.
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.