Aem community license required for local instances | Community
Skip to main content
rajashekharr629
rajashekharr629
New Participant
October 31, 2017
Solved

Aem community license required for local instances

  • October 31, 2017
  • 4 replies
  • 2557 views

I started to use community features on my local instances. I was following the adobe doc https://helpx.adobe.com/experience-manager/6-2/communities/using/deploy-communities.html  created community site on author and followed the steps to publish it. It got published but I am not able to configure any users on publish instance. Attached a screenshot which shows an error when try to open groups/members from community consoles and the log file errors as below.

log file from publish instance:-

31.10.2017 07:40:59.238 *ERROR* [0:0:0:0:0:0:0:1 [1509453659148] GET /communities/groups.html/content HTTP/1.1] com.adobe.cq.social.members.impl.CommunityMemberGroupImpl Unable to get id from resource

31.10.2017 07:40:59.238 *ERROR* [0:0:0:0:0:0:0:1 [1509453659148] GET /communities/groups.html/content HTTP/1.1] com.adobe.cq.social.members.impl.CommunityMemberGroupImpl Unable to get id from resource

31.10.2017 07:40:59.240 *ERROR* [0:0:0:0:0:0:0:1 [1509453659148] GET /communities/groups.html/content HTTP/1.1] com.adobe.cq.social.members.impl.CommunityMemberGroupImpl Unable to get id from resource

31.10.2017 07:40:59.550 *ERROR* [qtp112013173-13433] org.apache.felix.metatype Missing element AD in element OCD : bundle://431.0:0/OSGI-INF/metatype/com.adobe.cq.social.site.endpoints.impl.SiteOperationService.xml

31.10.2017 07:40:59.550 *ERROR* [qtp112013173-13433] org.apache.felix.metatype Missing element AD in element OCD : bundle://431.0:0/OSGI-INF/metatype/com.adobe.cq.social.site.impl.AnalyticsComponentConfigurationServiceImpl.xml

31.10.2017 07:40:59.550 *ERROR* [qtp112013173-13433] org.apache.felix.metatype Missing element AD in element OCD : bundle://431.0:0/OSGI-INF/metatype/com.adobe.cq.social.site.impl.SiteConfiguratorImpl.xml

31.10.2017 07:40:59.551 *ERROR* [qtp112013173-13433] org.apache.felix.metatype Missing element AD in element OCD : bundle://431.0:0/OSGI-INF/metatype/com.adobe.cq.social.user.endpoints.impl.CommunityUserOperationService.xml

31.10.2017 07:40:59.551 *ERROR* [qtp112013173-13433] org.apache.felix.metatype Missing element AD in element OCD : bundle://431.0:0/OSGI-INF/metatype/com.adobe.cq.social.user.endpoints.impl.UserProfileOperationService.xml

31.10.2017 07:40:59.551 *ERROR* [qtp112013173-13433] org.apache.felix.metatype Missing element AD in element OCD : bundle://431.0:0/OSGI-INF/metatype/com.adobe.cq.social.user.impl.transport.HttpToPublisherImpl.xml

^C

I have configured the following things on my local:-

  • configured replication agents
  • replicated the crypto key
  • enabled tunnel service
  • even checked for primary publisher configuration enabled or not. by default it's on.

notes:- I have only basic AEM 6.2 version(no hot fixes or feature packs).

Questions:-

1. Do I have to have separate community license(I have AEM6.2 license on my local)  to get community features to work on my local instance?

2. Do I have to install any additional packages on top of basic aem6.2 version if we get the community license?

3. I followed some demo videos (Scott's Digital Community: May 2016 Ask the Community Experts ) related to communities sent by smacdonald2008​.  There were saying they will be having additional features in aem6.3 like email notifications and some social integration plugins and additional features. if this is the case can we get additional community packages for aem6.2 version(assuming community license for aem6.2,we don't have any plans of upgrading to aem6.3 for now). Could you please guide me where to find the actual differences for aem6.2 communities vs aem6.3 communities.

thanks

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 neerav

The tunnel service should be enabled only on Author. Looks like you are trying to access Members console from a publish instance (port 4503 in screenshot). Please try accessing it from Author, it would use tunnel service to fetch users from Publish instance and allow you to manage site users/groups.

You can get an idea of all additional features in 6.3 in AEM communities from AEM Communities

These are also available as part of AEM Communities 6.2 Feature Pack 3. The feature pack can be downloaded from Package share.

Thanks,

Neerav

4 replies

N
neeravAccepted solution
Employee
November 6, 2017

The tunnel service should be enabled only on Author. Looks like you are trying to access Members console from a publish instance (port 4503 in screenshot). Please try accessing it from Author, it would use tunnel service to fetch users from Publish instance and allow you to manage site users/groups.

You can get an idea of all additional features in 6.3 in AEM communities from AEM Communities

These are also available as part of AEM Communities 6.2 Feature Pack 3. The feature pack can be downloaded from Package share.

Thanks,

Neerav

rajashekharr629
rajashekharr629Author
New Participant
November 3, 2017

I enabled the tunnel service on publish instance as well, now I am able to see the default groups/users. but according to AEM Docs, we need to enable only on author instance right.

thanks

raj

rajashekharr629
rajashekharr629Author
New Participant
October 31, 2017

thank you so much for your quick response. please keep me posted.

thanks

raj

smacdonald2008
smacdonald2008
New Participant
October 31, 2017

We asked the team to look at this question. YOu typically get additional packages on Package Share.

Terms & ConditionsAccessibility statement

Loading footer...