Issue with integrating with Brightcove Player with AEM

Forum|Forum|9 years ago
August 31, 2016
4 replies
2659 views

Hi All,

We have video component where all these videos are playing using Brightcove player(Adobe's clous service).Here we are seeing that videos are not playing and it's expecting index.min.js file from 'players.brightcove.net' domain but this not getting loaded at publish side and throwing 404 error.

Video are playing in author without any issue.

Attached screenshot from browser console.

Thanks,

Kishore

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 kautuk_sahni

Hi

Please have a look at this AEM bright Cove connector Official documentation.

Link:- https://github.com/coresecure/Adobe-CQ5-Brightcove-Connector/tree/master/current

//

Adobe AEM Brightcove Connector

This project integrates the Brightcove Video Cloud platform into Adobe Experience Manager (CQ5)

http://www.coresecure.com/brightcove-aem-integration

Supports

CQ 5.5, 5.6, 5.6.1
AEM 6.0, 6.1

One of the old Forum post related to AEM BrightCove Integration is here:- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__nwkp-hi_do_anyonekno.html

I hope this will help you.

Thanks and Regards

Kautuk Sahni

smacdonald2008

Level 10

Do you have any config settings on auth not on Pub. Something has to be different on Pub that would account for this behaviour.

GK-007Author

Level 9

smacdonald2008 wrote...

Do you have any config settings on auth not on Pub. Something has to be different on Pub that would account for this behaviour.

i have compared configurations in author with publish instance ,all are same no difference.

Do i need to do any configuration changes to allow this domai(players.brightcove.net)?

Thanks,

Kishore

smacdonald2008

Level 10

If you Google This subject, you will find an online guide that provides info. I recommend looking at that. If you follow that and still envounter this, there could be a bug. At that point, open a ticket. We have no community content that i can point you to for this use case.