You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Antonio Fallucchi <af...@ideato.it> on 2014/03/03 14:54:59 UTC
Best configuration for production
Hi,
could you tell me what is the best configuration for jackarabbit in
production?
Jackarabbit Standalone
Jackarabbit + tomcat + mysql persistent
other..
Thanks!
--
Antonio Giuseppe Fallucchi
System Administrator and Security Specialist
Ideato
af@ideato.it
Mobile: +39-347-4065233
Skype: fallucch
ideato srl - web ideas for sale
http://www.ideato.it
Phone: (+39) 0547 480114
Fax: (+39) 0547 19 50 205
via Giulio Pastore, 151
47522 Cesena (FC)
"Questo messaggio è destinato unicamente alla/e persona/e sopraindicata/e.
E' strettamente personale e può contenere informazioni la cui riservatezza
è tutelata dalla normativa ai sensi del DLgs 196/03. E' espressamente
vietato alla/e persona/e non destinataria/e leggere, copiare o comunque
usare questo messaggio o diffonderne il contenuto senza autorizzazione. Chi
ha ricevuto per errore questo fax o messaggio è pregato di distruggerlo e
di avvertire per telefono o fax o email, il mittente."
Re: Best configuration for production
Posted by Lukas Kahwe Smith <sm...@pooteeweet.org>.
On 03 Mar 2014, at 14:54, Antonio Fallucchi <af...@ideato.it> wrote:
> Hi,
>
> could you tell me what is the best configuration for jackarabbit in
> production?
>
> Jackarabbit Standalone
> Jackarabbit + tomcat + mysql persistent
> other..
Generally standalone isn’t recommended though I have seen it work quite well in production. Using a container can also ease deployment, which is especially useful for shops that have some experience in running Java setups.
regards,
Lukas Kahwe Smith
smith@pooteeweet.org
Re: Best configuration for production
Posted by Jaroslaw Marek <ja...@gmail.com>.
Hi,
Deploying Jackrabbit webapp in our own container (Tomcat) gives us
possibility to have a full control over it's configuration.
Moreover on http://jackrabbit.apache.org/standalone-server.html it says
that:
" The Jackrabbit Standalone server is designed primarily as a quick and
easy way to get a content repository up and running for testing and
development purposes. For more complex deployment scenarios and
configuration options you should look at the Jackrabbit Web Application
and Jackrabbit JCA Resource Adapter packages."
On 03/14/2014 10:10 AM, AshokBS wrote:
> Hi Jarek,
>
> Is Jackrabbit standalone same as using webapp? Any advantages or
> disadvantages using it?
>
>
>
> --
> View this message in context: http://jackrabbit.510166.n4.nabble.com/Best-configuration-for-production-tp4660402p4660525.html
> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
Re: Best configuration for production
Posted by AshokBS <as...@altimetrik.com>.
Hi Jarek,
Is Jackrabbit standalone same as using webapp? Any advantages or
disadvantages using it?
--
View this message in context: http://jackrabbit.510166.n4.nabble.com/Best-configuration-for-production-tp4660402p4660525.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
Re: Best configuration for production
Posted by Jaroslaw Marek <ja...@gmail.com>.
On 03/03/2014 02:54 PM, Antonio Fallucchi wrote:
> Hi,
>
> could you tell me what is the best configuration for jackarabbit in
> production?
>
> Jackarabbit Standalone
> Jackarabbit + tomcat + mysql persistent
> other..
>
> Thanks!
>
>
Hi,
I don't know if it's the best configuration for production, but we use
Jackrabbit webapp on tomcat in clustered configuration (2 nodes) backed
up with Oracle DB serving content via WebDAV. It hasn't been used that
extensively yet, but seems to be working fine.
Regards,
Jarek