Get replication agent id in Replication EventHandler | Community
Skip to main content
A
anands82757572
Level 2
April 19, 2018
Solved

Get replication agent id in Replication EventHandler

  • April 19, 2018
  • 15 replies
  • 8486 views

Hello All,

I am implementing a replication event handler and one of the requirements is to get the replication agent id for each of the activate processes.

This is snippet of what I have written in the handleEvent method

ReplicationAction replicationAction = ReplicationAction.fromEvent(event);

if (null != replicationAction) {

String path = replicationAction.getPath();

String type = replicationAction.getType() != null ? replicationAction.getType().toString() : "";

LOG.info("Replication triggered {} for {} ", type, path);

String strReplicationAgentId = replicationAction.getConfig() != null ? replicationAction.getConfig().getAgentId() : "";

LOG.info("ReplicationAgentId: {}", strReplicationAgentId);

}

The issue is that the strReplicationAgentIdis always null.

I know that this is based on the runmodes, but not sure how to get the agent ids involved in the replication event.

Any guidance on how to achieve this will be very helpful.

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 joerghoh

When you check the information available for a replication event (localhost:4502/system/console/events), you can see that there is no agentID contained in it.

I think, that the replication event is sent per replication action (for example per page), and not per agent ID. That means a single replication event stands for the replication of a single resource via all available/configured replication agents.

Jörg

15 replies

Vijayalakshmi_S
Vijayalakshmi_S
Level 10
April 19, 2018

Hi,

Can you try accessing any other methods of AgentConfig instead of getAgentId and see if you are able to get the result. Based on this, we can then narrow down to why we are not able to get the agentId.

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

A
anands82757572Author
Level 2
April 19, 2018

Hi,

I did some more debugging and see that the AgentConfig object returned by replicationAction.getConfig() itself is null.

So all methods for the AgentConfig return null.

That is very strange and I am clueless

D
dylanr46798176
Level 3
April 20, 2018

And you have an active replication agent? And whatever you publish actually gets replicated?

smacdonald2008
smacdonald2008
Level 10
April 20, 2018

We have an older community artilce that show how to create a Rep Event Handler -- Adobe CQ Help | Creating Replication Event Handlers for Adobe Experience Manager

We will update this soon to a more recent version of AEM.

A
anands82757572Author
Level 2
April 23, 2018

Yes, my replication agents are active and content is getting replicated successfully.

One thing I did notice in the logs further is that some how the event handler is getting invoked few seconds earlier than the actual replication happening.

Is this a possibility?

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
April 23, 2018

When you check the information available for a replication event (localhost:4502/system/console/events), you can see that there is no agentID contained in it.

I think, that the replication event is sent per replication action (for example per page), and not per agent ID. That means a single replication event stands for the replication of a single resource via all available/configured replication agents.

Jörg

Vijayalakshmi_S
Vijayalakshmi_S
Level 10
April 24, 2018

HI,

  • I tried writing Replication event handler and could reproduce the scenario you mentioned. (AgentConfig retrieved via Replication action is always null) Even another method getLog which returns ReplicationLog is also always null.
  • If we could observe the ReplicationAction API - ReplicationAction ("The Adobe AEM Quickstart and Web Application.") , constructors have params like action, path userId etc which we are able to successfully pull out on a Replication Event, while getConfig and getLog is more like setters and getters(from method summary) and not something that comes as is from action captured on a replication event.

Given this, If you could share the exact use case/requirement you are trying to achieve with agent configs, perhaps we can see if there are any other ways

A
anands82757572Author
Level 2
April 24, 2018

Thank you for looking into it.

We have a event audit functionality that feeds an audit log for page create/update/delete, asset create/delete, workflow start, active, deactivate events that in turn is fed to ELK where we have custom ops dashboards.

Specifically to the activate event, when a reviewer approves a workflow task, a series of activate events are triggered corresponding to the targeted replication agents.

As an example, I have publish, flush, test_target as the 3 configured agents. I see 3 events corresponding to page activate.

For proper reporting, I want to filter on only the "publish" events and filter the flush and test_target events, therefore trying to get the agentId from the replication action config.

Vijayalakshmi_S
Vijayalakshmi_S
Level 10
April 25, 2018

HI,

Could you please help clarify the inline comments(in italics)

Specifically to the activate event, when a reviewer approves a workflow task, a series of activate events are triggered corresponding to the targeted replication agents.  - - Are you using custom process step for approval/ replicating wherein you explicitly set the replication agents via "setFilter" of ReplicationOptions for replicator.replicate?

As an example, I have publish, flush, test_target as the 3 configured agents. I see 3 events corresponding to page activate. - Can you elaborate on this, especially - 3 events for page activate?

A
anands82757572Author
Level 2
April 25, 2018

Are you using custom process step for approval/ replicating wherein you explicitly set the replication agents via "setFilter" of ReplicationOptions for replicator.replicate?

Yes, I have a custom process step. The agent names are fetched from the process args and then we set to ReplicationOptions

for(String agentId : agentIdsArray) {

                            try{

                            agentIdFilter = new AgentIdFilter(agentId);

                                    replicationOptions = new ReplicationOptions();

                                    replicationOptions.setFilter(agentIdFilter);

Can you elaborate on this, especially - 3 events for page activate?

This is in the step properties for my generic replicator (as we call it)

So, if I publish a page, it hits the various configured agents and I see as many log entries.

Hope this helps.

Show more replies
Terms & ConditionsAccessibility statement

Loading footer...