You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by ro...@apache.org on 2015/03/23 17:22:01 UTC

svn commit: r1668678 - /sling/site/trunk/content/documentation/the-sling-engine/the-sling-launchpad.mdtext

Author: rombert
Date: Mon Mar 23 16:22:01 2015
New Revision: 1668678

URL: http://svn.apache.org/r1668678
Log:
SLING-4050 - Make it easier to run launchpad on Oak/Mongo

Document the run modes and slightly adjust the documentation with oak specifics.

Modified:
    sling/site/trunk/content/documentation/the-sling-engine/the-sling-launchpad.mdtext

Modified: sling/site/trunk/content/documentation/the-sling-engine/the-sling-launchpad.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/the-sling-launchpad.mdtext?rev=1668678&r1=1668677&r2=1668678&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/the-sling-launchpad.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/the-sling-launchpad.mdtext Mon Mar 23 16:22:01 2015
@@ -15,7 +15,8 @@ The following is a list of uses for the
 * `org.apache.sling.launchpad.base.jar` --  This is the *Launcher JAR* file used by the Standalone Application or the Web Application to start the OSGi Framework. This file is initially placed when first starting Sling and may later be updated by updating the system bundle with a new *Launcher JAR*.
 * `felix` -- The directory into which the Apache Felix Framework places the bundles, which have been installed into the system. This does generally not need to be touched.
 * `config` -- The directory into which the Apache Felix Configuration Admin Service stores the configurationes. Do not change any files in this directory, since changes will not generally be picked up.
-* `jackrabbit` -- The directory in which the Apache Jackrabbit JCR repository is started. Amongst other things this also contains the Jackrabbit configuration file `repository.xml`. You may modify this file, but don't forget to restart the Embedded Jackrabbit Repository bundle after doing this.
+* `jackrabbit` -- The directory in which the Apache Jackrabbit JCR repository is started ( only applicable when using Apache Jackrabbit 2.x ). Amongst other things this also contains the Jackrabbit configuration file `repository.xml`. You may modify this file, but don't forget to restart the Embedded Jackrabbit Repository bundle after doing this.
+* `oak` - The directory in which the Apache Jackrabbit Oak JCR Repository is started ( only applicable when using Apache Jackrabbit Oak with the SegmentNodeStoreBackend ).
 * `logs` -- Contains the log files generated by Sling. By default this contains the error.log and its rotated generations.
 
 
@@ -162,4 +163,10 @@ The *Launchpad App* and *Launchpad WebAp
 * Take the *Launchpad Bundles* artifact and unpack it
 * Finally pack all together into a single big JAR or WAR file
 
+The artifacts can be configured to use different JCR repository implementations, based on the value of the `-Dsling.run.modes` property. The following run modes are available for the 8-SNAPSHOT version of the Sling Launchpad:
+
+* `jackrabbit` ( default ): configures and starts up an Apache Jackrabbit 2.x JCR repository implementation
+* `oak`: configures and starts up an Apache Jackrabbit Oak repository implementation with a SegmentNodeStore ( TarMK ) implementation
+* `oak,oak_mongo`: configures and starts up an Apache Jackrabbit Oak repository implementation with a DocumentNodeStore implementation connected to a MongoDB database
+
 That's it. The resulting artifact may be directly used to launch the Standalone Java Application or may directly be deployed into any Servlet API 2.4 (or later) compliant servlet container.
\ No newline at end of file