Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

AEM 6.3 - Publishing of assets not binaryless

Avatar

Avatar
Validate 1
Level 1
seemad20428873
Level 1

Likes

2 likes

Total Posts

1 post

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
Applaud 5
View profile

Avatar
Validate 1
Level 1
seemad20428873
Level 1

Likes

2 likes

Total Posts

1 post

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
Applaud 5
View profile
seemad20428873
Level 1

06-07-2019

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 ?

View Entire Topic

Avatar

Avatar
Give Back 5
Level 3
anujg3325839
Level 3

Likes

27 likes

Total Posts

26 posts

Correct Reply

8 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 5
Boost 3
View profile

Avatar
Give Back 5
Level 3
anujg3325839
Level 3

Likes

27 likes

Total Posts

26 posts

Correct Reply

8 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 5
Boost 3
View profile
anujg3325839
Level 3

06-07-2019

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.