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
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'.
Oak Segment Tar NodeStore service
default is true.
Also stated in Gems presentation:
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.
Says use .cfg (Last Published: October 31, 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.