Month: December 2014

AEM 5.6.1 with Dispacther on IIS 7 Content not displayed

I came across a very unique problem today during one of my production deployment.

IIS with dispatcher on Windows Server and AEM 5.6.1

All Set up and networks good, however when hitting some CQ5 page on web server URL, not showing correct content/synced up content.

  1. Dispatcher.any, Logs, publish agent , Flush agent, accessed  URL directly on browser.
  2. then finally realized DefaultAppPool setting is needed to be increased for this problem to be resolved and it worked.

Reverse Replication AEM/CQ5 Pros and Cons [User Generated, User Profiles and as restful Service]

All Commercial products offers solution as larger aspect of enterprise that’s where it is critical for  Architect/solution developer to understand the nitty gritty of out of box module in relation with business requirement. You would fins many helpful posting regarding reverse replication .
This is one of the most comprehensive one

You need to ask a question why you need Reverse Replication , Please verify your requirements on this?

1. User profiles needed to be reverse replicated because has some user preference data, Does that moderation needed on author side?
2. Is it anonymous data ?
3. How many Publish you have in your setup? is it Non-Cluster setup or clustered setup amongst publish?
4. what’s volume of content in typical working hours (>10000 or <10000).

Let us come on Solution now

Solution 1.

If your publish is non-cluster and you think user generated node might go more than 10000 in a days, hold your hand and this is going to cause trouble for you, you need to use restful Service and store user generated data on one location. You can have separate Solr Data repository or have one additional publish  server and use that only for user data repository + service. Don’t go on reverse replication path out of box of AEM/CQ5.

Solution 2.

If Publish are clustered , Even more than 10000 user generated data would not be a issue.

Reverse replication can be implemented in couple of way

1. Enable outbox on publish
2.Enable Reverse replication agent on Author to poll user generated content so that it could retrieve data.
3. Create or use out of box activate workflow through Workflow Launcher as soon as new content is available on auhtor to push it across other publish in network