Skip to main content

Install Brightcove Sitecore connector 10.1 and above

Brightcove Sitecore connector 10.0 and below use the Media Framework which is depricated by Sitecore. Brightcove Sitecore connector 10.1 and above instead using the Data Exchange Framework. 
Before starting these steps, take a note of a few video pages in the environment you are setting up. That way you can refer to these pages after the upgrade to make sure these videos pages continue to work. Follow these steps in the following order. 

1. Install the Sitecore Installation package: Data Exchange Framework 6.0.0 rev. 01537 via Sitecore installation wizard. 

 2. For CM just package install would be sufficient (Takes around 30 min). For CD we would need to copy files (unzip the package and copy the files in the "Files" folder) over. 

 3. Run Cleanup script migration-cleanup.ps1 from root Sitecore site. This script is found in the full source code download of the connector. 

4. Install Brightcove Video connect package [example: Brightcove.Video.Connect.for.Sitecore-10.1.X-37]

5. Similar to previous data exchange, For CM just package install would be sufficient (Takes around 30 min). For CD we would need to copy files (unzip the package and copy the files in the "Files" folder) over. 

6. In Sitecore, Go to media library/Brightcove and create a new bright cove account 

7. Use these values to connect Brightcove to Sitecore . You can get this from your Brighcove account admin page -> API Authentication -> Add Application 

Account ID: 
Client ID: 
Client Secret: 

8. To configure Brightcove in Sitecore
a) Go to system/data exchange and create a tenant Note : Add/update Your account to the default tenant name while creating it. 
b) Click on the newly created tenant and enable admin permission as mentioned on the page https://integrations.support.brightcove.com/sitecore/configuration.html 
Note: Only do steps 1) Create Brightcove Tenant and 2) Configure a Brightcove Endpoint 

9. Move the video items from old location to new location. This steps is assuming that you are upgrading from a Brightcove connector 10.0 or earlier. If not, you can skip this step
 FROM: 
/sitecore/media library/Media Framework/Accounts/Your Brightcove/Media Content/2022
/sitecore/media library/Media Framework/Accounts/Your Brightcove/Media Content/2023
/sitecore/media library/Media Framework/Accounts/Your Brightcove/Media Content/2024 

 TO: 
/sitecore/media library/Brightcove/Your Brightcove/Videos/2022
/sitecore/media library/Brightcove/Your Brightcove/Videos/2023
/sitecore/media library/Brightcove/Your Brightcove/Videos/2024 

10. Search for video files in the following location: /Sitecore/media library/Brightcove/Your Brightcove/Videos 

11. Find a Video and play it by clicking on the "Preview" button in the Brightcove ribbon in Sitecore. 

12. Test out video pages to make sure they are working after the upgrade 

13. You can check if videos in Brightcove are coming into Sitecore by going to /sitecore/system/Data Exchange/Your Brightcove Tenant/Pipeline Batches/Pull Pipeline Batch and clicking on the "Run Pipeline Batch" button in the Data Exchange ribbon 

14. Lastly you can add Scheduled tasks in /sitecore/system/Tasks/Schedules that point to /sitecore/system/Tasks/Commands/Data Exchange/Run Selected Pipeline Batches Command 
and choose what pipelines you want to run (push, pull or sync) 

That's it. Happy Sitecoreing!
By

Comments

Post a Comment

Popular posts from this blog

Sitecore: Get list of logged in users

By
I had a deployment today and wanted to find a list of users who were logged into the Sitecore admin site. This was mainly so that I can contact them and let them know that a deployment was going to happen. I found the following link very useful as it gave me exactly what I was looking for. A list of users that were logged in and I contacted them. It also has the ability to Kick off users! http://{YourWebsite}/sitecore/client/Applications/LicenseOptions/KickUser Note: You can only see other users in this list if you have the right administrator permission. Logging in with a lower access level user only gave me the logged in user and no one else on the list.
Post a Comment
Read more

Sitecore clear cache setting

By
Sitecore has extensive cache settings. You can add caching at the rendering level so it affects all instances of that rendering. Or you can add caching at the component level on a particular page via the presentation details. This is all good when you are setting it up, but once this goes to production, the way caching is supposed to work is that the cache should get cleared after an item is published. So after an item is published, any associated cache should also automatically get updated. In our case, we saw that once we went to production (with extensive caching enabled) our pages loaded much faster. However when the content authors were updating content, the updates were not making it to the delivery servers. The content seemed to be stuck in the cache. We noticed that we had to do one of the following to see the updated cache. Go to the admin cache page [SitecoreSite/sitecore/admin/Cache.aspx] and click the "Clear all" button. This is not viable long term solution ...
Post a Comment
Read more

Using Okta Authentication for a Sitecore client site

By
I recently had a project where we had to add a new Sitecore site to an already multi site Sitecore 8.2 Update 7 instance. This new site had to integrate with Okta to manage user authentication. I found many articles online that integrated Okta and Sitecore's admin interface but I could not find one that just integrated Okta with a client Sitecore site. My first step was to use Okta's available ASP.NET MVC projects on their Dev site and test them out. This worked very well with the first Authenticated method I tried which was WS-Fed. But when I tried to use the same authentication method with a site in Sitecore I got errors in my logs like the following: Sitecore.Security.Principal.SitecoreIdentity does not contain a definition for Claims Claims are available in HttpContext.User.Identity but not in Sitecore.Security.Principal.SitecoreIdentity, and since we are using a Sitecore site we could not read the claims. I tried to make claims work in Sitecore using various online a...
1 comment
Read more