The advantage of having multiple repositories is that they can reside on different server instances. You can create multiple repositories on different server instances, deploy a single repository on a single server instance, and deploy applications on multiple repositories on a single server instance.
This topic includes the following information:
As an alternative to the steps in this section, a server-repo plugin is available to perform this configuration for you. Visit the Samples section for further details.
Creating multiple repositories on a single server instance
You can create multiple repositories on Geronimo. You can add a second repository to deploy your applications and leave Geronimo in its default repository.
Creating a repository besides the default repository
To add a second repository besides the default repository, take the following steps:
- Start Geronimo.
- Create a directory repo2 under
<geronimo_home>
, for example,<geronimo_home>/repo2
. - Create a file
repo2.xml
under the<geronimo_home>/repo2
directory, for example:repo2.xml<module xmlns="http://geronimo.apache.org/xml/ns/deployment-1.2"> <environment> <moduleId> <groupId>org.example.configs</groupId> <artifactId>myrepo</artifactId> <version>2.2</version> <type>car</type> </moduleId> <dependencies> <dependency> <groupId>org.apache.geronimo.framework</groupId> <artifactId>j2ee-system</artifactId> <type>car</type> </dependency> </dependencies> <hidden-classes/> <non-overridable-classes/> </environment> <gbean name="Repo2" class="org.apache.geronimo.system.repository.Maven2Repository"> <attribute name="root">repo2/</attribute> <attribute name="resolveToServer">false</attribute> <reference name="ServerInfo"> <name>ServerInfo</name> </reference> </gbean> <gbean name="Local2" class="org.apache.geronimo.system.configuration.RepositoryConfigurationStore"> <reference name="Repository"> <name>Repo2</name> </reference> </gbean> </module>
- Deploy the
repo2.xml
from the command prompt:
deploy(.bat|.sh) deploy <Geronimo_HOME>/repo2/repo2.xml
.
To verify that the repository is successfully deployed, you can list the targets on the current server with the command:
deploy(.bat|.sh) list-targets
, and you can see the following information:Available Targets: org.apache.geronimo.framework/j2ee-system/2.2/car?ServiceModule=org.apache.geronimo.framework/j2ee-system/2.2/car,j2eeType=ConfigurationStore,name=Local org.example.configs/myrepo/2.2/car?ServiceModule=org.example.configs/myrepo/2.2/car,j2eeType=ConfigurationStore,name=Local2
- Update the
etc/org.ops4j.pax.url.mvn.cfg
file, add the new second repository to theorg.ops4j.pax.url.mvn.defaultRepositories
property
The propertyorg.ops4j.pax.url.mvn.defaultRepositories
maintains a comma-delimited list of repositories that are used by the run-time server.
The format is:file:
< /absolute/path/to/repo2 >@snapshots
And if a variable it used, the new repository just deployed would be defined as:And the resulting property would be set to something that looks like this:file:${org.apache.geronimo.server.dir}/repo2@snapshots
The first defined repository is the default and primary GERONIMO_HOME/repository, the second one is the new repo2 repository just created.org.ops4j.pax.url.mvn.defaultRepositories=file:${karaf.home}/repository@snapshots,file:${org.apache.geronimo.server.dir}/repo2@snapshots
In Geronimo 3.0, there is a minor bug that exists when creating additional repositories for Geronimo instances. The files GERONIMO_HOME/var/config/config.xml
and GERONIMO_HOME/var/config/config-substitutions.properties
must exist even though they are never used, otherwise Geronimo will fail complaining that they do not exist. Simply create these files, or copy them from GERONIMO_SERVER/var/config/...
to work around this issue.
See GERONIMO-6284 for details.
Deploying an application to the repository
Here is an example of deploying a sample jsp application to the repository repo2.
- List the targets on the current server via the command:
deploy(.bat|.sh) list-targets
, and you can see the following information:Available Targets: org.example.configs/myrepo/2.2/car?ServiceModule=org.example.configs/myrepo/2.2/car,j2eeType=ConfigurationStore,name=Local2 org.apache.geronimo.configs/j2ee-system/2.2/car?ServiceModule=org.apache.geronimo.configs/j2ee-system/2.2/car,j2eeType=ConfigurationStore,name=Local
- Set the environment variable REPO2:
On a Windows system set REPO2=org.example.configs/myrepo/2.2/car?ServiceModule=org.example.configs/myrepo/2.2/car,j2eeType=ConfigurationStore,name=Local2
On a non-Windows system export REPO2=org.example.configs/myrepo/2.2/car?ServiceModule=org.example.configs/myrepo/2.2/car,j2eeType=ConfigurationStore,name=Local2 - Deploy the application to the repository repo2 with the following deploy (.bat or .sh) command:
On a Windows system deploy.bat deploy --targets %REPO2% <SAMPLE_HOME>/applications/geronimo-jsp-examples/target/geronimo-jsp-examples-2.2.war
On a non-Windows system deploy.sh deploy --targets $REPO2 <SAMPLE_HOME>/applications/geronimo-jsp-examples/target/geronimo-jsp-examples-2.2.war
where <SAMPLE_HOME> is the directory of your samples. Then, the jsp example is deployed to the new repository repo2. The following message is displayed:Deployed org.apache.geronimo.applications.examples/geronimo-jsp-examples/2.2/war @ /jsp-examples
- Access the application at http://host:port/jsp-examples.
To undeploy the application from the repository repo2, run the following deploy (.bat or .sh) command:
On a Windows system deploy.bat undeploy "%REPO2%|org.apache.geronimo.applications.examples/geronimo-jsp-examples/2.2/war"
On a non-Windows system deploy.sh undeploy "$REPO2|org.apache.geronimo.applications.examples/geronimo-jsp-examples/2.2/war"
Creating multiple repositories on multiple server instances
Create several server instances, and start the server instances. For information about creating server instances, see Running multiple Geronimo instances. Then you need to create several repositories on these server instances. You can test the repositories by deploying an application to these server instances and undeploying the application from these server instances.
Creating a repository for server instance2
After you create more than one server instance, you can create repositories and deploy the repositories to different server instances. For information about how to create and deploy a repository on a server instance, see the following example that creates repo22 and deploys it on server2:
- Create a directory repo22 under
<geronimo_home>
, for example,<geronimo_home>/repo22
. - Create a file
repo22.xml
under the<geronimo_home>/repo22
directory. For detailed information about the file, see creating multiple repositories. - Deploy the
repo22.xml
by running the following command from the command prompt:
deploy(.bat|.sh) -port instance2_RMI_port deploy <geronimo_home>/server2/repo22/repo22.xml
You can follow the same steps to create repositories for server instance3.
Deploying a sample application to and undeploying it from the repository
To test the repository that you create, you can deploy a sample application to and undeploying it from the repository.
- Set the environment variable repo22 for the repository repo22 that you have previously created.
- Deploy the application to the repository repo2 with the following deploy (.bat or .sh) command:
On a Windows system deploy.bat -port instance2_RMI_port deploy --targets %repo22% <SAMPLE_HOME>/applications/geronimo-jsp-examples/target/geronimo-jsp-examples-2.2.war
On a non-Windows system deploy.sh -port instance2_RMI_port deploy --targets $repo22 <SAMPLE_HOME>/applications/geronimo-jsp-examples/target/geronimo-jsp-examples-2.2.war - Undeploy the jsp application from repo22 repository with the following command:
On a Windows system deploy.bat -port instance2_RMI_port undeploy %repo22%|org.apache.geronimo.applications.examples/geronimo-jsp-examples/2.2/war
On a non-Windows system deploy.sh -port instance2_RMI_port undeploy $repo22|org.apache.geronimo.applications.examples/geronimo-jsp-examples/2.2/war
You can follow the same steps to deploy applications to and undeploy applications from repositories on server instance3.