TarMK Farm Configuration in 6.x | Community
Skip to main content
R
rajeev_yadav
Level 4
July 25, 2016
Solved

TarMK Farm Configuration in 6.x

  • July 25, 2016
  • 14 replies
  • 3868 views

I was going through AEM 6.1  TarMK setup. Here, we have multiple AEM instances with its own TarMK. Author is setup to replicate changes to all instances while changes in from publish are replicated using reverse replication to author and replication to all instances. 

But the problem here is that AEM 6.1 has stopped reverse replication of UGC and users. Reverse replication only works for pages. So what if I have any component for UGC in AEM implementation. Does that mean, I should never go for farm implementation? Setting up MongoDB is the only option?

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 suryalamech

You can still use a farm deployment model for your publish instances, however; starting with 6.1, UGC requires the use of Mongo SRP or Adobe SRP. To be clear, the SRP is only for UGC, other site content can continue to reside in the TarMK. More details can be found here - https://docs.adobe.com/docs/en/aem/6-2/administer/communities/srp.html

14 replies

Show previous replies
JK_Kendall
JK_Kendall
Level 9
July 26, 2016

 "setting up Mongo for a cluster on the publish tier is not recommended"

Be aware - the recommendations for the platform store and for UGC store are different as the storage locations and characteristics of working with the various forms of content are not the same.

For example, from MSRP - MongoDB Storage Resource Provider

MongoDB Replica Set

For the production environment, it is strongly recommended to setup a replica set, a cluster of MongoDB servers that implements master-slave replication and automated failover.

- JK

AnkurAhlawat-1
AnkurAhlawat-1
Level 6
July 27, 2016

Yes rajeev, By default, author will poll for changes every 30 seconds.  To alter this interval  you can modify polling interval in below osgi servic from felix console.

Apache Sling Distribution Trigger - Scheduled Triggers Factory

regards,

Ankur Ahlawat

AEM CQ5 Tutorials

O
Adobe Employee
ogillAdobe Employee
Adobe Employee
July 27, 2016

JK Kendall wrote...

 "setting up Mongo for a cluster on the publish tier is not recommended"

Be aware - the recommendations for the platform store and for UGC store are different as the storage locations and characteristics of working with the various forms of content are not the same.

For example, from MSRP - MongoDB Storage Resource Provider

MongoDB Replica Set

For the production environment, it is strongly recommended to setup a replica set, a cluster of MongoDB servers that implements master-slave replication and automated failover.

- JK

 

Hi Janice,

my advice was in response to your comment about a publish cluster:

>In AEM 6.2,  JSRP (JCR SRP)  is suitable for production on a publish cluster, but the UGC will still not be visible on author, so moderation will need to take place on publish.  In order to moderate on author, you need MSRP (MongoDB) or ASRPP (Adobe cloud).

When talking about a "publish cluster", I assume you are talking about AEM clustering with MongoDB, which like I said is not recommended.

From the docs[0]: "JSRP is the default provider for accessing all UGC on a single AEM instance" 

If a client wishes to use MSRP with a publish farm, then as you rightly point out, Mongo recommend a replica set. 

Regards,

Opkar

[0] https://docs.adobe.com/docs/en/aem/6-2/develop/communities/scf/srp.html#JSRP

JK_Kendall
JK_Kendall
Level 9
July 27, 2016

Hi Opkar,

Opkar Gill wrote...

...When talking about a "publish cluster", I assume you are talking about AEM clustering with MongoDB, which like I said is not recommended.

From the docs[0]: "JSRP is the default provider for accessing all UGC on a single AEM instance" 

If a client wishes to use MSRP with a publish farm, then as you rightly point out, Mongo recommend a replica set. 

Regards,

Opkar

[0] https://docs.adobe.com/docs/en/aem/6-2/develop/communities/scf/srp.html#JSRP

 

The quote from the docs is in the developer section in regards to what you get OOTB when setting up a single author and single publish.

If you go to topologies section [1] you'll see there is a reference to an Oak cluster (though I make no claim to expertise on setting up AEM for production!)

Hope that helps.

[1] Recommended Topologies for Communities : For Production

- JK

Terms & ConditionsAccessibility statement

Loading footer...