AEM | Replication Event | Community
Skip to main content
prabodh
prabodh
Level 2
July 4, 2018
Solved

AEM | Replication Event

  • July 4, 2018
  • 2 replies
  • 1281 views

Hi,

I need to capture an event(activate/deactivate) and perform some operations, only when the content is delivered to publish instance. Suppose, I have 2 publish instances, how do I get to know when the content is successfully published to both?

Tried with the ReplicationStatus API, but to no avail. Is there any API available that gives me the confirmation when a replication event is successful.

Could anyone suggest me a way to figure out this, please?

Regards,

Prabodh

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Gaurav0669

    Hi,

    I think replication event listener can help for the same, deployed on your publisher server. Have a look at the ReplicationAction API.

    ReplicationAction ("The Adobe AEM Quickstart and Web Application.")

    Thanks,

    Gaurav

    2 replies

    Gaurav0669
    Gaurav0669Accepted solution
    July 4, 2018

    Hi,

    I think replication event listener can help for the same, deployed on your publisher server. Have a look at the ReplicationAction API.

    ReplicationAction ("The Adobe AEM Quickstart and Web Application.")

    Thanks,

    Gaurav

    joerghoh
    Adobe Employee
    joerghohAdobe Employee
    Adobe Employee
    July 4, 2018

    If you want to retrieve this information on author, it's going to be hard; not because it's actually hard to gather this information, but rather because there might be unforseen cases, which you should consider upfront. And maybe you should re-think your application design.

    For example, how to you want to handle the case, that one of your publish instances is down for a moment (e.g. 5 minutes) or for an more extended period of time. Would your approach be able to cope with that situation in a way that you still can reach your business goals?

    I would try to avoid that approach and choose a different way.

    regards,

    Jörg

      Terms & ConditionsAccessibility statement

      Loading footer...