Content Replication Process - Security - Governance

[sud_varun]

Hello,

I have a scenario where 1 Author instance replicates its content to 1 Publish instance.

Now, at the infrastructure level, how does the replication process follows between two different applications (author and publish)?

Is there a security layer attached and wrapped around the content that flows from one instance to another?

How do we ensure that the replicated content is not corrupted during its transport?

How does AEM/CQ prepares the content that gets replicated to the publish instance?

Thank you in advance!

Varun

[justin_at_adobe · Accepted solution]

AEM uses a proprietary binary format for replication called Durbo. Durbo includes the necessary checksumming to ensure that replicated content is not corrupted during transport. If it is, the replication receiver servlet (on publish) will reject it and the replication sender (on author) will retry. In terms of security, you can use either basic authentication or MSSL for authenticating the replication request.

Regards,

Justin

[smacdonald2008]

When AEM performs replication - it uses HTTP to send information (a servlet in the publish environment receives the request ) from author to publish. 

Security assumes that your servers on secure as well in your corporate network. 

Test the replicated content. When you replication content - check the log files to ensure that there are no errors and the content was successfully replicated. Typically an AEM admin performs this task. 

Here is an overview - taken from docs:

REPLICATING FROM AUTHOR TO PUBLISH

Replication, to a publish instance or dispatcher, takes place in several steps:

• the author requests that certain content be published (activated); this can be initiated by a manual request, or by automatic triggers which have been preconfigured.
• the request is passed to the appropriate default replication agent; an environment can have several default agents which will always be selected for such actions.
• the replication agent "packages" the content and places it in the replication queue.
• in the Websites tab the colored status indicator is set for the individual pages.
• the content is lifted from the queue and transported to the publish environment using the configured protocol; usually this is HTTP.
• a servlet in the publish environment receives the request and publishes the received content; the default servlet ishttp://localhost:4503/bin/receive.
• multiple author and publish environments can be configured.

For more information - https://docs.adobe.com/docs/en/aem/6-1/deploy/configuring/replication.html

[sud_varun]

justin_at_adobe wrote...

AEM uses a proprietary binary format for replication called Durbo. Durbo includes the necessary checksumming to ensure that replicated content is not corrupted during transport. If it is, the replication receiver servlet (on publish) will reject it and the replication sender (on author) will retry. In terms of security, you can use either basic authentication or MSSL for authenticating the replication request.

Regards,

Justin

Perfect. Thanks!

[rajeev_yadav]

Is Durbo binary format used in AEM 6.x as well?

[Jörg_Hoh]

Durbo is used in AEM 6.x as well.

Jörg

[rajeevy89244319]

Thanks jorg.. where can i get info about durbo format? Can you please share resources or links

[Jörg_Hoh]

The format is not publicly documented.

[rajeevy89244319]

ohk.. is it specifically created for aem by adobe?

[Jörg_Hoh]

yes