Hi Tarek,
I assume you've seen Jackrabbit documentation [1]. We use the last model
- Standalone Repository Server - for two reasons:
1. We can scale cluster of applications servers and cluster of
repository servers independently.
2. More than one application can use the same repository.
What we did is we took jackrabbit-webapp and we deployed it in a Tomcat
configured by us and "inject" our own repository.xml configuration [2]
(it is different than using jackrabbit-standalone.jar).
Other thing is how you want to connect to your repository. In case of
standalone server there are two options:
* RMI
* WebDAV
Whichever protocol you choose, you can either use JCA from within your
application or create Repository object manually.
Coming to your question about administrating the repository - as far as
I know there is no perfect tool for that. I tried Toromiro [3] and JCR
Explorer [4], both have pros and cons. I haven't tried CLI tool yet, but
I would imagine it would be possible to use that. I will try.
Cheers,
Jarek
[1] http://jackrabbit.apache.org/deployment-models.html
[2] http://wiki.apache.org/jackrabbit/Clustering
[3] http://www.subshell.com/en/toromiro/jcr-browser-editor/
[4] http://www.jcr-explorer.org/
On 03.10.2014 23:00, Tarek Jarraya wrote:
Hi All,
We want to use jackrabbit 2.8 with the following needs:
- We use only servlet container Tomcat 7. Maybe it is a constraint for JCA
adapter deployment mode.
- We want to be able to have access to administrate the repository : multi
access channels
The only mode that can match is the standalone. But based on the wiki
description is more adapted for quick start not for real production purpose.
I have deployed the war version on tomcat, but unfortunately I can not
access to it with the CLI tool based on the standalone jar.
Which deployment model do you advice me?
Thank you,
Tarek
