Page History

{scrollbar}

• bin
• jsr88
• lib
• schema

The repository is shared, and contains lots of basic and important libraries are required to bootstrap server. It is possible to configure second repositories, one fore each instance. See Configuring multiple Repositories.

• repository

Each instance gets its own copy of the following at <geronimo_home>/<instance_name> . These are read-write and are necessary for each Geronimo instance.

• etc
• repository
• var

These are also read-write but are not part of the minimally necessary directories and files for running a Geronimo instance, but may be desired. The deploy directory will be automatically created when you start Geronimo if it does not already exist.

• repository (this is not the same as the primary shared repository)
• deploy
• hotbundles

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

...

1. Create a directory foo under <geronimo_home>.
2. Copy var, repository and etc directories to foo. You can use the command deploy:new-server-instance to help you with this step.
3. Optionally create foo/repository and set it up as a second repository for the Geronimo instance.
4. 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.

...

• First download the Geronimo bundle distribution
• Determine what you want GERONIMO_HOME to be. We will use /opt/geronimo3 for this example.
• Unpack the Geronimo bundle, and move the unpacked directory to /opt/geronimo3
• We'll create two Geronimo instances named gserv1 and gserv2
  • Create the Geronimo instance directories as /opt/geronimo3/gserv1 and /opt/geronimo3/gserv2
  • Copy the directories var, etc, and repository to each instance directory
  • Modify the gservN/var/config/config-substitutions.properties file for each Geronimo instance changing the PortOffset. We'll set the PortOffset for gserv1 to 100 and the PortOffset for gserv2 to 200 for our example.
  • Create a start script in each Geronimo instance directory to make it easier to start each instance
    • /opt/geronimo3/gserv1/start.sh

      No Format
      borderStyle solid
      #!/bin/bash # Geronimo start script # instance: gserv1 # Uncomment this to explicitly set Geronimo's runtime Java #JAVA_HOME=/usr/jdk1.6.0_25 #PATH=${JAVA_HOME}/bin:${PATH} export GERONIMO_HOME=/opt/geronimo3 export GERONIMO_SERVER=${GERONIMO_HOME}/gserv1 export GERONIMO_OPTS=-Dorg.apache.geronimo.server.dir=${GERONIMO_SERVER} cd ${GERONIMO_SERVER} # Normal startup ${GERONIMO_HOME}/bin/startup # Interactive startup #${GERONIMO_HOME}/bin/geronimo run

    • /opt/geronimo3/gserv2/start.sh

      No Format
      borderStyle solid
      #!/bin/bash # Geronimo start script # instance: gserv2 # Uncomment this to explicitly set Geronimo's runtime Java #JAVA_HOME=/usr/jdk1.6.0_25 #PATH=${JAVA_HOME}/bin:${PATH} export GERONIMO_HOME=/opt/geronimo3 export GERONIMO_SERVER=${GERONIMO_HOME}/gserv2 export GERONIMO_OPTS=-Dorg.apache.geronimo.server.dir=${GERONIMO_SERVER} cd ${GERONIMO_SERVER} # Normal startuo ${GERONIMO_HOME}/bin/startup # Interactive startup #${GERONIMO_HOME}/bin/geronimo run

  • On linux, make the start script is executable with chmod: chmod 755 start.sh
• Your Geronimo installation file structure should look something similar to this:

  No Format
  borderStyle solid
  /opt/geronimo3 |-- LICENSE |-- NOTICE |-- README.txt |-- RELEASE_NOTES-3.0-SNAPSHOT.txt |-- bin |-- deploy |-- etc |-- gserv1 | |-- etc | |-- repository | |-- start.sh | `-- var |-- gserv2 | |-- etc | |-- repository | |-- start.sh | `-- var |-- hotbundles |-- jsr88 |-- lib |-- repository |-- schema `-- var

• Finally you can start up each instance by executing their associated start script you just created in the previous step

...