Peržiūrite versijai skirtą žinyno turinį:
One of the most important changes in AEM 6 are the innovations at the repository level.
Currently, there are two node storage implementations available in AEM6: Tar storage, and MongoDB storage.
Įspėjimas:
The PID for the Segment node store has changed from org.apache.jackrabbit.oak.plugins.segment.SegmentNodeStoreService in previous versions of AEM 6 to org.apache.jackrabbit.oak.segment.SegmentNodeStoreService in AEM 6.3. Make sure you make the necessary configuration adjustments to reflect this change.
By default, AEM 6 uses the Tar storage to store nodes and binaries, using the default configuration options. To manually configured its storage settings, follow the below procedure:
-
Edit the file and set the configuration options. The following options are available for Segment Node Store, which is the basis of AEM's Tar storage implementation:
- repository.home: Path to repository home under which various repository related data is stored. By default segment files would be stored under the crx-quickstart/segmentstore directory.
- tarmk.size: Maximum size of a segment in MB. The default is 256MB.
-
Make sure that MongoDB is installed and an instance of mongod is running. For more info, see Installing MongoDB.
-
Configure the node store by creating a configuration file with the name of the configuration you want to use in the crx-quickstart\install directory.
The Document Node Store (which is the basis for AEM's MongoDB storage implementation) uses a file called org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService.cfg
-
Edit the file and set your configuration options. The following options are available:
- mongouri: The MongoURI required to connect to Mongo Database. The default is mongodb://localhost:27017
- db: Name of the Mongo database. By default new AEM 6 installations use aem-author as the database name.
- cache: The cache size in MB. This is distributed among various caches used in DocumentNodeStore. The default is 256
- changesSize: Size in MB of capped collection used in Mongo for caching the diff output. The default is 256
- customBlobStore: Boolean value indicating that a custom data store will be used. The default is false.
- mongouri: The MongoURI required to connect to Mongo Database. The default is mongodb://localhost:27017
-
Create a configuration file with the PID of the data store you wish to use and edit the file in order to set the configuration options. For more info, please see Configuring Node Stores and Data Stores.
Each update to the repository creates a new content revision. As a result, with each update the size of the repository grows. To avoid uncontrolled repository growth, old revisions need to be be cleaned up to free disk resources. This maintenance functionality is called Revision Cleanup. The Revision Cleanup mechanism will reclaim disk space by removing obsolete data from the repository. For further details about Revision Cleanup, read the Revision Cleanup page.
„Twitter™“ ir „Facebook“ skelbimams „Creative Commons“ sąlygos netaikomos.