Seamless Media Migration to XM Cloud: A Step-by-Step Guide from Sitecore XP 10.4 and Content Hub Integration - Part 1

-

 We have been working with Sitecore and the media library for a long time. Now if the requirement comes from the client to use Sitecore Content Hub instead of Sitecore media library, and they are also planning to move  from Sitecore XP to XMCloud, then the following questions will pop up

  • How to connect Sitecore Content Hub
  • How to make sure all the Images in the Sitecore Media library are added to the Sitecore content hub 
  • How can we add the Sitecont Content Hub assets public link to all the Images from the Media library referenced
  • How to migrate all content from Sitecore XP to XM Cloud

Let's explore the migration step by step as follows

  • Connect Sitecore XP with Sitecore Content Hub
  • Migrate all the Sitecore XP Media Items to Sitecore Content Hub
  • Configure public link creation for all the assets migrated from the Sitecore media library
  • Replace all the media item references with the public link of the assets
  • Sitecore Content Hub integration with XM Cloud
  • Migration of content from Sitecore XP to Sitecore XM Cloud
Connecting Sitecore XP with Sitecore Content Hub.

Steps:
  • Download Sitecore Connect™ for Content Hub SIF Package 
  • Download Sitecore Connect™ for Content Hub WDP Package
  • Unzip the Sitecore Connect™ for Content Hub SIF Package and add the Sitecore Connect™ for Content Hub WDP Package.zip to this folder.
  • Open Windows PowerShell in administrator mode and run the following file deploy.ps1 available in the folder Sitecore Connect™ for Content Hub


  • Open the deploy.ps1 and update the following settings before executing this deploy.ps1
    • ScchWdpPackage  - "$($PSScriptRoot)\Sitecore.Connector.ContentHub.WDP.5.2.96-r00458.5768.scwdp.zip"
    • InstanceName - your Sitecore XP 10.4 instance
    • InstanceUrl - your Sitecore XP 10.4 website URL
    • SitecoreAdminUser - Admin user
    • SitecoreAdminPass - Admin password
    • SqlInstanceName  - SQL instance from connectionstring.config, usually the prefix of the database created before _core
      Example: if the core database name is sclocal104_core, then the SqlInstanceName will be "sclocal104"
    • SqlUser - SQL user name from connectionstring.config
    • SqlPass - SQL password from connectionstring.config
    • SqlServerName - SQL server name from connectionstring.config
    • SkipDatabaseInstallation -  $true

  • Go to the extracted SIF folder location and execute the deploy.ps1 



  • After the above script is successfully executed, content from the WDP package will be deployed to the Sitecore CMS along with some newly added settings to the connectionString.config file. Here, we will target only the DAM module, so the CMP module-related settings in the ConnectionStrings.config file will be commented out.
    • DAM.ExternalRedirectKey value should be Sitecore


  • Open Sitecore Content Hub and get the following information for replacing the ConnectionString.config settings variable shown above.
    • ClientId
    • ClientSecret
    • UserName
    • Password
  • To get the ClientId and ClientSecret from Content Hub, go to Manage -- OAuth clients 
    Find LogicApp and click the Quick edit icon to get its ClientId and ClientSecret


  • We need to create a new user for this purpose instead of using the superuser, which would be provided for accessing the whole Content Hub feature.
  • To create a User, go to Manage--User and provide the username, and click Save


  • After the user is created, click on Edit Profile and provide the email address, which will be used to reset the password.


  • Click on Reset password to update the password that will be used in our connectionstring.config file.
  • Go to User Group and find the M.Builtin.SitecoreDAM.Everyone, click on the Policies icon and from the Rules tab, click on the New Rule button, select M.Asset, with  Read and ReadPublicLinks access 

Now, assign the User Group to the TESTDAM user we created, and add the following to the User Group.
Before Assigning the M.Builtin.SitecoreDAM.Everyone 
  • Now we have all the information ready, let's update the values in the Connectstring.config.
  • Go to the web.config file and add Content-Security-Policy settings for making the DAM module and Sitecore communicate without any issue.
    Here, replace https://playground.sitecoresandbox.cloud with the Content Hub URL            
<add name="Content-Security-Policy" value="default-src 'self' 'unsafe-inline' 'unsafe-eval'                                https://apps.sitecore.net; 
img-src 'self' data: https://playground.sitecoresandbox.cloud/;
style-src 'self' 'unsafe-inline' https://fonts.googleapis.com;
font-src 'self' 'unsafe-inline' https://fonts.gstatic.com;
upgrade-insecure-requests; block-all-mixed-content;
child-src 'self' https://playground.sitecoresandbox.cloud/;
connect-src 'self' https://playground.sitecoresandbox.cloud/;
media-src https://playground.sitecoresandbox.cloud/;" />

  • Add the CORS in Sitecore Content Hub to have the local Sitecore CMS URL.



  • Restart the Sitecore CMS, and let's see the DAM module installed in CMS, and changes to Rich Text Editor, General Link, and Image controls.

    DAM module:

    • Mapping from Content hub to Sitecore defined field will be done like below.

      • Transformation can be done by adding the transformation item in the DAM module and enabling it by the image control.





        RichText Editor:

        In RTE, a new icon has been added that will help to add the DAM-approved assets in the RTE. This will be the public link to the DAM assets from different renditions. The User can select any rendition and add the image to RTE.





        Image:

        The user can able to add DAM assets using the different transformations on the selected asset.
         





        General Link:



Part 2
Part 3

Let's learn and grow together, happy programming 😊

Comments

Post a Comment

Popular posts from this blog

Sitecore Upgrade from 8.1 XP to 10.4 XM Scaled - Part 1

-
Image
 I have seen many questions about upgrading Sitecore from 8.1 to 10.4. I will share my experience upgrading Sitecore with tips and tricks that will help the upgrade process go smoothly. This contains multiple parts to get started with the upgrade activity. Steps for Sitecore and Solution Upgrade Checklist Sitecore 8.1 Local instance setup with Solr and verification Sitecore 10.4 Code upgrade issues and resolution Steps for Sitecore and Solution Upgrade Checklist: Solution Upgrade Checklist:   Task Comments / Findings Comments 1 .Net 4.8 upgrade to all the projects in the solution   2 Install SQL Server 2022   3 .NET Core 6.0 Windows Hosting Bundle   4 Install Compatible Solr version for 8.1 and 10.4   5 Update the Nuget package of Sitecore from 8.1 to 10.4 ...
Read more

Custom Item Url and resolving the item in Sitecore - Buckets

-
Image
I have a situation to update the Item URL to be SEO friendly as my items in content tree looks like below. In the above image in order to resolve the item, Sitecore will find the item from the below URL http://domainname/en/dine/nv/chicken but I need to form a URL that is more SEO friendly like http://domainname/en/chicken In Sitecore by Out of box, we can achieve this by using Aliases , we can create an Aliases under System à Aliases and in the Linked Item field select the target item. But this is very tedious as we need to go to every item in the content tree and create Aliases, instead of that we will be going to do it programmatically using custom pipelines. ·          Link Provider (Provides the custom URL for the item based on the templates) ·          Item Resolver (Resolves the item based on the custom URL generated by CustomLinkProvider , that we going to create later...
Read more

Fixing Sitecore Buckets folder path - Items created after 12 AM server time zone

-
Image
We are working on a 24/7 content publishing site, so it is important to have articles published on the correct date and time.  We are using Sitecore buckets to manage article items. In the Sitecore content tree, when the content author tries to look at the items created after 12 AM server time, the items are created under the previous day folder only,  but it is supposed to be created in the current day folder( ie. new bucket day folder to be created and the items to be added in this new day folder ). We have hosted the site in Azure VM in the UAE region. UAE is 4 hours ahead of GMT/UTC (UTC+04:00) so items created between 12 AM to 4 AM are always created under the previous day's folder, but when the item created after 4 AM is properly created under the current day folder in the content tree. Example: If the item was created on 2024 à 09 à 24 between 12 AM to 4 AM then still the item is made under the bucket folder of 2024 à 09 à 23 The created date and the updated ...
Read more