...
- set the
org.apache.geronimo.server.name
system property to the instance name before you start the server. Use the syntax-Dorg.apache.geronimo.server.name=foo
to name your instance foo. Add this to yourGERONIMO_OPTS
environment variable, or pass it on the java command-line invocation of the server. The server's var directory will then be in <geronimo_home>/foo.org.apache.geronimo.server.name
may be any pathname relative to (descending from) <geronimo_home>. Theorg.apache.geronimo.server.dir
system property may also be used, and it overridesorg.apache.geronimo.server.name
. Userg.apache.geronimo.server.name
to specify an absolute path, which need not be relative to <geronimo_home>.
Otherwise, the two system properties behave the same. mkdir foo
- Copy var to foo.
- Start the server.
Multiple Repositories
First, we consider the case single server instance case, and just add a second repository. Say we want to leave Geronimo in its repository, but add a second repository to deploy our applications. Adding a second repository is pretty easy. 1. Create
- Create a plan (say repo2.xml) for your repository module.
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<module xmlns="http://geronimo.apache.org/xml/ns/deployment-1.2"> <environment> <moduleId> <groupId>org.example.configs</groupId> <artifactId>myrepo</artifactId> <version>2.0-SNAPSHOT</version> <type>car</type> </moduleId> <dependencies> <dependency> <groupId>org.apache.geronimo.configs</groupId> <artifactId>j2ee-system</artifactId> <version>2.0-SNAPSHOT</version> <type>car</type> </dependency> </dependencies> <hidden-classes/> <non-overridable-classes/> </environment> <\!--Repository--> <gbean name="Repo2" class="org.apache.geronimo.system.repository.Maven2Repository"> <attribute name="root">repo2/</attribute> <reference name="ServerInfo"> <name>ServerInfo</name> </reference> </gbean> <\!--Configuration Store service--> <gbean name="Local2" class="org.apache.geronimo.system.configuration.RepositoryConfigurationStore"> <reference name="Repository"> <name>Repo2</name> </reference> </gbean> </module> |
...
- Create the repository's root directory.
...
-
mkdir <geronimo_home>/repo2
- The directory is specified by the root attribute of the Maven2Repository GBean,
repo2/
in the above example. It is a path relative to the base directory
- The directory is specified by the root attribute of the Maven2Repository GBean,
...
- <geronimo_
...
- home>.
...
...
- A resolveToServer attribute is being added to allow this path to be relative to baseServer, which is useful with multiple server instances.
...
- Deploy the repository module by deploying repo2.xml.
Using the new repository is a little tricky, and is only supported from the command line currently. The essence is to use the --targets option of the deploy command to target your module to deploy in your new repository. First, use the deployer list-targets command to see the repositories. The target names are long and cumbersome:
...