But I do not know to which server I must send the request. We have an architecture of 1 author server replicating to 2 publish instances, each one of those behind a dispatcher.
Thanks for your help, I'm a bit confused on how this feature works.
One more thing you can do is, Let impression information to be collected on publish instance as usual and then reverse replicate it to author. Impression informations are stored under /var/statistics/pages. You can create a launcher for reverse replication for modification event under this node.
Or to be simple, use any analytics service (GA or something :))
One more thing you can do is, Let impression information to be collected on publish instance as usual and then reverse replicate it to author. Impression informations are stored under /var/statistics/pages. You can create a launcher for reverse replication for modification event under this node.
Or to be simple, use any analytics service (GA or something :))
Yes but as you might have guessed already, typically in production author server is in a non-DMZ, and not accessible from the user's browser issuing the request.
Normally you need to configure Day CQ WCM Page Statistics to be pointed to an author CQ instance (default is http://localhost:4502) therefore you can see stat in a siteadmin under impressions column (shows the activity on a page in number of hits.)
Do you ever run into issues where reverse replicating Impressions in this manner causes data loss for high-traffic sites? It seems that, even if your reverse replication processes run every few seconds, your three instances (two publish) may step on each other a bit. Just curious.
By the way, the better approach is definitely to use a dedicated web analytics platform for measurement. Though there is some use in having the up-to-date page impressions in context within AEM.
