AEM6.3 configure repository like 6.1, tarmk only, documentation bugs | Community
Skip to main content
B
bobkranson
Level 4
November 6, 2017
Solved

AEM6.3 configure repository like 6.1, tarmk only, documentation bugs

  • November 6, 2017
  • 5 replies
  • 3291 views

Hi Forum,

We are interested in initializing the repository in AEM 6.3 to be the same as the configuration for AEM 6.1 to the extent that it uses the new 6.3 Oak version and retains utilizing only the tarmk node, blob, and document store.

I've run into issues trying to disable the default repository initialization.  I wonder if others on the forum have experienced these issues or whether there are some details that I need to address them? ie. make sure you do X,Y,Z, or maybe be sure you verify this or that so the repository initialization works.  The trick is that we need to establish the repository before installing the SP1 so I'm stuck on how to get the repository without seeing repository/blobids,datastore,index, and segmentstore.  I only want segmentstore!

I essentially followed the instructions but alas no avail.  I'm posting the documentation bugs I encountered to improve the next publish update from Adobe.

In the meantime, any advice or details from the user field for initializing the repository as tarmk-only?  Thanks in advance....and now some doc bugs:

Adobe Documentation Bugs Monday November 6, 2017

https://helpx.adobe.com/experience-manager/6-3/sites/deploying/using/data-store-config.html
Last Published: November 3, 2017

1. "customBlobStore: Boolean value indicating that a custom data store is used. The default value is false."

The default value is 'true'.

http://localhost:4502/system/console/configMgr
Oak Segment Tar NodeStore service

default is true.

Also stated in Gems presentation:
https://docs.adobe.com/ddc/en/gems/Managing-AEM-DataStore.html

2. "To use TarMK with the S3 Datastore, you need to start AEM using the crx3tar-nofds runmode, for example:"

The crx3tar-nofds option still creates blob datastores.

Runmodes documentation does not describe, explain, or specify this new runmode supplied by Adobe.

3. https://helpx.adobe.com/experience-manager/6-3/sites/deploying/using/storage-elements-in-aem-6.html
Says use .cfg  (Last Published: ‎October‎ ‎31‎, ‎2017)

https://helpx.adobe.com/experience-manager/6-3/sites/deploying/using/data-store-config.html
Says use .config

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by smacdonald2008

Thank you for putting this list together - we created a doc bug based on this thread as well.

5 replies

smacdonald2008
smacdonald2008
Level 10
November 6, 2017

We passed this thread to the Doc Manager for AEM.

    B
    bobkransonAuthor
    Level 4
    November 6, 2017

    Thanks for documentation follow-up.

    The "why" for this activity is to do a 1-to-1 migration for the tarmk segment store between versions (6.1 -> 6.3) before splitting or introducing additional complexities for blob or custom data stores.  I see and understand the "why" for the default splitting of the node/segment/blob stores by re-reviewing the Gems presentation, but for larger repositories we want to be sure things work as they did and then advance the configuration to leverage the new features.

    smacdonald2008
    smacdonald2008Accepted solution
    Level 10
    November 6, 2017

    Thank you for putting this list together - we created a doc bug based on this thread as well.

    B
    bobkransonAuthor
    Level 4
    November 7, 2017

    Following this up with a Day Care support ticket to engage/verify creating initial repository without datastore and blob configuration.

    B
    bobkransonAuthor
    Level 4
    November 8, 2017

    Clarification from a peer review: it does inline the blob store with the documented .config setting.  My misinterpretations was to see the additional directories in the /repository folder.  Question will be is it safe to delete the extra directories...blobids, datastore?

    "SegmentNodeStoreBuilder{blobStore=inline}" with the .config file customBlobStore=B"false" observed in error.log.

    SegmentNodeStoreBuilder{blobStore=DataStore
    backed BlobStore [org.apache.jackrabbit.oak.plugins.blob.datastore.OakFileDataStore]}     is the default with 6.3 without specifying the .config file.

    Terms & ConditionsAccessibility statement

    Loading footer...