The following configuration options are available: The document node store is the basis of AEM’s MongoMK implementation. The following is a sample. file: #Path to repo The default value is true for AEM 6.3 and later versions. The default maximum is 256MB.ĬustomBlobStore: Boolean value indicating that a custom data store is used. Tarmk.size: Maximum size of a segment in MB. By default, segment files are stored under the crx-quickstart/segmentstore directory. : Path to repository home under which repository-related data is stored. Make sure you make the necessary configuration adjustments to reflect this change. The PID for the Segment node store has changed from. in previous versions of AEM 6 to .segment.SegmentNodeStoreService in AEM 6.3. Edit the file to set the configuration options. To configure both the node store and the data store, perform these steps:Ĭopy the AEM quickstart JAR file to its installation directory.Ĭreate a folder crx-quickstart/install in the installation directory.įirst, configure the node store by creating a configuration file with the name of the node store option you want to use in the crx-quickstart/install directory.įor example, the Document node store (which is the basis for AEM’s MongoMK implementation) uses the file .Įdit the file, and set your configuration options.Ĭreate a configuration file with the PID of the data store you want to use. Each OSGi configuration is referenced using a persistent identifier (PID).
The binary data is stored in a data store, whereas content nodes are stored in a node store.īoth data stores and node stores can be configured using OSGi configuration. In Adobe Experience Manager (AEM), binary data can be stored independently from the content nodes. Configuring node stores and data stores in AEM 6 Introduction