Asset Management

General

In AEM 6.3, binary data can be stored independently from the content nodes.

• The binary data is stored in a data store
• Content nodes are stored in a node store

Resources

Migration

• OAK Repository Migration - from the Apache Jackrabbit documentation - this is not specific to AEM.

• Using the CRX2Oak Migration Tool - Adobe's version of the Jackrabbit Oak document.

• Configuring node stores and data stores in AEM 6 - This has specific instructions for MongoMK and S3, and some information about FileDataStore. We should be able to meld the two to get what we want.

• For migrating to MongoMK with an S3 Data Store:

java -Xmx4096m -jar aem-quickstart-6.3.0.jar -v -x crx2oak -xargs -- --load-profile mongo-custom-ds -T mongo-uri=mongo://mongo-host:mongo-port -T mongo-db=mongo-database-name

• AEM 6 - Migrating to FileDataStore from embedded segmentstore binaries - Simple step-by-step, but seems to be TarMK only.

• AEM Convert Blob Datastore to File Datastore - Blog from some person, but seems to jive with what others say.

• All the Secrets of Repository Migration - SlideShare has some troubleshooting tips, advice about using the extension vs. stand-alone crx2oak (we probably should use the stand-alone).

Replication

• How to Verify that Binary-less Replication is Actually Being Used - We will be moving to 'binary-less' replication.
• How to Share the Data Store Between Author and Publish Instances - Note this is for CQ 5.6.1, so not clear how much this applies to our 6.3+ instances.
• Shared Data Store - Nice architecture diagram, but otherwise light on details (this is really a plug for some consulting service). Note the last step is to change the serialization type, which was described in prior entry "How to Share the Data Store Between Author and Publish Instances"

Assets (General)

• The Digital Asset Explosion & AEM Assets - a webinar about the growth of assets (size, number, expectaions, etc).