Hi Tony,
On 04.06.2010 15:53, Anthony Giaccone wrote:
>
>
> I want to deploy a production level sling system. To do that I have to
> go beyond what's offered in the launchpad.
Basically the launchpad should get your started with just about anything
you might need for your application.
>
> I want to install jackrabbit as a stand alone war file.
>
> Then link sling to talk to that instance of jackrabbit.
I personally think that running Jackrabbit embedded in Sling is the best
option from the perspective of systems management, ease of use,
performance etc.
And if you are not required to use a specific servlet container, I would
go for the Sling standalone application which has quite nice start/stop
control (run java -jar org.apache.sling.launchpad.app-5-incubator.jar
-help to get a list of command line options for the standalone application).
>
>
> First is this a reasonable way to do the deploy? Second, how do I do that?
You can deploy Sling and Jackrabbit as two separate web applications in
the same servlet container, but I would not recommend it, because it
brings close to no value and is complicated to set up.
If you still want to go that route, you have to:
* put the jcr.jar and jackrabbit-api.jar into a shared class laoder
of the servlet container
* configure Sling to use the JCR and Jackrabbit API using
bootclassloading
* replace the Embedded Jackrabbit bundle by the Client Jackrabbit
bundle
* Ensure the Sling Client Jackrabbit bundle can access the the
repository through JNDI (see jackrabbit docs for more information).
Regards
Felix
>
>
> Is there a document that describes how to set up a production sling
> environment?
>
>
> Tony Giaccone
>
