...

• bin
• lib
• schema
• repositorydata

Each instance gets its own copy of the following at <geronimo_home>/<instance_name>

• var
• deploy (hot deployment)
• etc
• repoository

The bin, lib and schema directories are read-only, and thus may be are shared between instances. The repository is also not shared, which means that an application deployed in one instance will only show up in the list of deployed modules in all the other instances, but only shown running in of the deployed instance.

Creating a new server instance

Start with a fresh image of geronimoGeronimo. Do not use an image that has been used to run the default instance.

...

1. Create a directory foo under <geronimo_home>.
2. Copy var, repository and etc directories to foo. Starting from v2.2, you You can use a GShell the command deploy/new-instance to help you with this step.
3. Edit foo/var/config/config-substitutions.properties and change the portOffset. Try using any integers such as 1, 2, 10, 20, 30.. for various instances.

Running an instance

1. Set the org.apache.geronimo.server.name system property to define a server name before you start the server. This system property is null by default, defining the server instance at <geronimo_home> as the default instance. Use the syntax -Dorg.apache.geronimo.server.name=foo to change the server name to an instance named foo located at <geronimo_home>/foo. Add this to your GERONIMO_OPTS environment variable:

...

The Administrative Console can also be used for all these operations. Connect to an instance by using the right HTTP port (default 8080).

Further readings

To use multiple repositories see Configuring multiple Repositories.