Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

AEM 6.3 - Publishing of assets not binaryless

Avatar

Level 1

HI All,

We see binaries being  replicated, despite binaries replication (S3) being used and configured.

we did the required configuration in replication agents and can see with the help of proxy agents that data(binaries ) are being transferred between author and publish server.

Inatslled the com.adobe.granite.oak.s3connector-1.6.4.zip
Copy …/config/org.apache.jackrabbit.oak.plugins.blob.datastore.SharedS3DataStore.config to /crx-quickstart/install/ on author and publisher
Configure shared S3 repository on author and publisher
Copy crx-quickstart/install/org.apache.jackrabbit.oak.segment.SegmentNodeStoreService.config to /crx-quickstart/install/ on author and publisher
Set content to customBlobStore=B”true"
Set Runmode of author and publisher to
CQ_RUNMODE=….,crx3tar-nofds,crx3
Change replication on author to binaryless replication
Serialization Type: Binary less
Transport URI: http://localhost:4503/bin/receive?sling:authRequestLogin=1&binaryless=true

are there more configration to make it work ?

1 Accepted Solution

Avatar

Correct answer by
Level 3

You might be missing secret key in s3 datastore.config

Try to add the key value pair (secret="somerandomvalue") in org.apache.jackrabbit.oak.plugins.blob.datastore.SharedS3DataStore.config

This file should be same across all the aem connecting to the S3 bucket. It should resolve your issue.

View solution in original post

1 Reply

Avatar

Correct answer by
Level 3

You might be missing secret key in s3 datastore.config

Try to add the key value pair (secret="somerandomvalue") in org.apache.jackrabbit.oak.plugins.blob.datastore.SharedS3DataStore.config

This file should be same across all the aem connecting to the S3 bucket. It should resolve your issue.