Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.
SOLVED

AEM sites & unified user generated content

Avatar

Level 5

1) This link https://docs.adobe.com/docs/en/aem/6-1/deploy/communities/topologies.html refers  communities/topologies rather is there any separate deployment link for AEM site/topologies which has site content & user generated in the same site and rather UGC seen as AEM communities ?

Does the Social resource provider (adobe social / mongo db) works along with AEM site (on tarMK) as in below table or does it works only with AEM communities

2) If it works along with AEM sites what are the additional licensing required ?

3) Please share any idea of how the below MSRP or ASRP works for a site with end user preferences & his social activity & streams ? 

Recommended : MSRP or ASRP

 

                      
MicroKernelSITE CONTENT
REPOSITORY
USER GENERATED CONTENT
REPOSITORY
SOCIAL RESOURCE PROVIDERCOMMON STORE 
anyJCRMongoDBMSRPYes
anyJCRAdobe Social
cloud
ASRPYes
1 Accepted Solution

Avatar

Correct answer by
Employee

1) These topologies are equally valid for AEM Sites deployed along with AEM Communities on the same instances, and on standalone deployments for AEM Communities. 

2) AEM Communities does indeed require a dedicated SKU. In terms of persistence options - only ASRP requires an additional SKU known as the "AEM Communities On Demand Extension", as it ends up storing the Community content on hosted (by Adobe) servers. With MSRP, you will have to run your own instances of MongoDB/SOLR. 

3) Both MSRP and ASRP have been designed to handle these scenarios. End user preferences always remain in the publish instances, and they are synchronized with the new Sling Distribution since the release of AEM 6.1 Activites and social streams always go into the "Common Store" for user generated content, hence accessible directly from all publish instances.

Hope this clarifies!

View solution in original post

8 Replies

Avatar

Correct answer by
Employee

1) These topologies are equally valid for AEM Sites deployed along with AEM Communities on the same instances, and on standalone deployments for AEM Communities. 

2) AEM Communities does indeed require a dedicated SKU. In terms of persistence options - only ASRP requires an additional SKU known as the "AEM Communities On Demand Extension", as it ends up storing the Community content on hosted (by Adobe) servers. With MSRP, you will have to run your own instances of MongoDB/SOLR. 

3) Both MSRP and ASRP have been designed to handle these scenarios. End user preferences always remain in the publish instances, and they are synchronized with the new Sling Distribution since the release of AEM 6.1 Activites and social streams always go into the "Common Store" for user generated content, hence accessible directly from all publish instances.

Hope this clarifies!

Avatar

Level 9

A Community Site is a customized instance of an AEM Site.  

If you plan to have features which allow site visitors to enter content from a publish instance, what is referred to as 'community content' or 'user generated content (UGC)', then you need a way to manage UGC, especially if using a tarMK farm of publish instances.

If you want to use the common store of UGC accessed through the Social Resource Provider (SRP) API, such as your reference to MSRP or ASRP, then you need to licence AEM Communities (which includes AEM Sites). 

From SRP - Community Content Storage - "Note : The SRP API is available only to licensed customers of AEM Communities."

From ASRP - Adobe Social Common Store - 'The "AEM Communities: OD Add-On Extension" SKU is necessary for integration with the Adobe Social cloud.'

I hope this is helpful.

- JK

Avatar

Level 5

Thanks JK .I get the details on the licensing but Few more questions that can clarify this better.

1) Is there a way i can store user profile & his preference along with UGC in Adobe Social or MongoMk and still control them with in AEM site user management console (  for the users / groups)

2) Why is not an end user updating his profile & preferences not seen as UGC , this is also transnational and  even with sling distribution sync up across publish is needed which only avoids the author instances getting the node synced up ?

3) Is there any updates to AEM architecture to support unified user profile and preference in a common repository which can cater portal like solution?

4) And on the other hand why MongoMk is recommended only for distributed content authoring and not on site that require portal like nature which needs its own DB for some custom user data ?

Avatar

Level 9

Answers from Bertrand :

Q1) Is there a way i can store user profile & his preference along with UGC in Adobe Social or MongoMk and still control them with in AEM site user management console (  for the users / groups)

A1) No, there isn't.

Q2) Why is not an end user updating his profile & preferences not seen as UGC , this is also transnational and  even with sling distribution sync up across publish is needed which only avoids the author instances getting the node synced up ?

A2) Because user profile attributes and preferences are used across many AEM features beyond UGC, hence they need to be generally available to AEM via regular APIs. Yes, Sling distribution is the right way to do this.

Q3) Is there any updates to AEM architecture to support unified user profile and preference in a common repository which can cater portal like solution?

A3) This can be achieved today if running a publish side cluster – but for storing UGC this will only be supported for production in 6.2.

Q4) And on the other hand why MongoMk is recommended only for distributed content authoring and not on site that require portal like nature which needs its own DB for some custom user data ?

A4) Because most customers are still using AEM for web content publishing where a farm of read only TarMK instances is the best option – but there are valid scenarios for publish clusters also.

- JK

Avatar

Level 5

Thanks Bertrand  and JK.

on

A3) This can be achieved today if running a publish side cluster – but for storing UGC this will only be supported for production in 6.2.

1) What is this publish side cluster is this a new feature enabled for TarMK AEM 6.2  based repositories (repository level cluster) like it was in CRX2 (depreciated ) or

2) is thus cluster for  UGC is referred from MongoDB cluster for publish instances from an MongoMK perspective.

I assume as of now AEM 6.1 supports publish TarmK farms only (which are individual repositories) and not a cluster at repository level as in CRX2(deprecated) 

Are there any new features available from AEM 6.2 for the above?

Avatar

Level 5

Any additional pointers on upcoming publish cluster options for tarMK repositories with reference to the questions

Avatar

Level 9

Hi Sri,

For serious, in-depth architecture discussions, it is recommended you work through your account representative.

- JK