Development environment

Defining Geronimo server runtimes and servers

In this section we discuss various options to configure your development environment.

Editing a Server configuration

In order to edit the configuration of a server, double click on server in the Servers view to open the overview of the server as shown below.

• General Information
  Edit the fields in this section to change the name of the server or to associate the Geronimo Server with a different Apache Geronimo v2.1 Runtime or to change the hostname with which the Geronimo Server is associated.
• Security Credentials
  The default User ID is system with a password manager. If your server installation uses a different set of credentials, change these accordingly. These security credentials configured here are used to detect server status as well as deploying and undeploying of applications.
• Automatic Publishing
  All servers use the default publishing settings. The server can be configured to not publish automatically by selecting the Never publish automatically option. The default publish setting can be overridden by selecting the Override default settings option and providing a new Publish interval.
• Port Configuration
  The default HTTP and RMI ports are 8080 and 1099 respectively. If your server installation uses a different HTTP and/or RMI port, edit these values accordingly. Altering the values here does not change the corresponding ports in the associated Geronimo Server Runtime.
• Console Output
  The default server console output log level is INFO. If you want to enable debug output to console, select DEBUG.
• Server Startup
  The settings under this section control the ping thread that polls to the server to detect the server status when the server is started from within eclipse. Ping delay specifies the time the ping thread will wait before polling the server. Ping interval controls the time between successive pings. Maximum Pings is the number of times the ping thread will poll the server to detect a successful startup. If the server startup can not be confirmed, the ping thread will stop the server.
  In case of a remote server, Ping interval controls the time between successive pings to update the server status.
• Server VM Arguments
  Any additional arguments to be passed on to the server VM can be specified here.

Creating and Using a Custom Server Assembly

In this section we discuss how to use the Geronimo Eclipse Plugin to create and use a custom server assembly.

Creating a Custom Server Assembly

In order to create a custom server assembly, you must already have a Geronimo Server installed and started. The popup menu on the running server has a "Launch Server Custom Assembly" menu on it. Clicking this menu item will bring up the Server Custom Assembly dialog that is shown below.



Enter in the pertinent information and select all the plugins that you desire to have in the new server. The "Geronimo Assembly :: Boilerplate Minimal" plugin MUST be selected in order to create a working server. The working server will be placed in the specified directory. A tar ball or zip file will also be placed in the "var/temp" directory of the running server for easy distribution.

Using a Custom Server Assembly

Now that we have created the custom server assembly above, it is time to use it. Stop the original server and uninstall it (easiest done by using the Windows Preferences dialog via the Server Runtime Environments page). Use the same method that you used to install the original server with one small difference. This time, point to the directory where the newly created server is.



In place of the full Geronimo server that you started with, you should now have a valid custom Geronimo Server.

Other configuration