Communities license understanding

[sandeepk7656774]

Hi All,

I have AEM 6.1. I can see already see communities module and see various administration options under (http://aemhost:port/communities/admin/defaultsrp). This Link tells that "The SocialResourceProvider API is available only to licensed customers of AEM Communities.". In OSGI bundles I could see APIs bundles related SRP

There is Search component and API also there, as seen in above screenshot.

I am able to connect a Mongo instance as MSRP and add comment using comment component, which gets added to Mongo, also indexed to Solr instance (though faced an issue that collection has to be already there).

Is it like, when we use APIs it would check for license? Please help understand.

Thanks
Sandeep

[JK_Kendall · Accepted solution]

If you go into production with a site that uses the Communities capability, you should have a license for it.

You can experiement with it in a development environment without paying for a license.

That's my understanding.  If I don't quite have it right, I'm sure someone else will reply.

- JK

[apanghal]

Sandeep,

What Janice explained is true for all production usages of AEM communities as an independent module.

That specific licensing requirement is for those AEM customers who have licenses for other modules (but not of AEM communities) running in production setup but want to extend their Sites/Assets capabilities using SRP services to store their content in cloud/mongo/rdb. Though SRP  services are available as part of AEM quickstart but to use those in production for extended use cases of other AEM modules (e.g. Sites, Assets, Mobile)  , customer need to have communities license.    

-ashok

[reghunathp92822]

How about using the OOTB Handlebar Engine(This is wrapped within SocialComponentHelper) to develop Basic CMS components using Handlebars instead of Sling. Does it requires Adobe Communities license?

We are not talking anything related to communities or SRP or any UGC stuff.

Thanks

RP