|Home > Index > Apache Aries Samples running in Geronimo 3.0|
It is possible to install and run several of the Apache Aries sample EBAs in Apache Geronimo 3.0-SNAPSHOT. These are OSGi enabled Web Applications and other bundles that leverage capabilities such as Blueprint, JNDI, JDBC, JPA, and JTA in OSGi specified ways. The samples are packaged in an EBA for deployment. The current samples are the Aries Blog and AriesTrader.
You can find more details on the samples here:
You can download an image of the "Geronimo Non-Certified Web Container" (either Tomcat or Jetty) from this location:
Geronimo 3.0-M1 download page
You must use a Web Container image and not a "Little-G" (minimal) version of the server. The Little-G version does not include necessary components for deploying the Apache Aries samples.
Follow the Apache Geronimo documentation to unpack and start the server image (Hint: unzip or untar the server image and use something like "./bin/geronimo.sh run" to start the server).
There are several choices to obtain the Apache Aries EBA samples.
In either case, you can find the necessary downloads (source or EBA artifacts) at this location:
Latest Apache Aries Release
If you choose not to build the samples you can skip to Deploy the Aries Samples DataSource
Download and unzip the source zip for the Latest Apache Aries Release of Aries Samples and build the project.
This procedure will pull in the binaries from the latest release and its dependencies.
What you are really interested in here are the sample EBAs for Blog and AriesTrader which can be found at:
Each of the two samples requires a Datasource. However, before you can deploy the Datasources you need to obtain the tranql-connector-derby-embed-xa rar. Unfortunately, this was not included in the Geronimo 3.0-M1 server images (but will be included in future images).
After you have both of the necessary files in your local file system use the following command to deploy the datasource:
Deploy the Blog or AriesTrader EBAs using the Geronimo web console or the following commands (NOTE: you should only deploy one version of each sample at a time - for example only the jdbc Blog or jpa Blog sample and not both concurrently):
You should now be able to access the samples as follows:
For details on how to interact with the Samples and the sample structure reference the following links: