CRM and CX Blogs by SAP
Stay up-to-date on the latest developments and product news about intelligent customer experience and CRM technologies through blog posts from SAP experts.
cancel
Showing results for 
Search instead for 
Did you mean: 
graeberm
Explorer
In SAP Marketing Cloud 2102, we enhanced the Simple Content Repository by providing the new repository domain smc-content.s4hana.ondemand.com. The new repository domain provides a much faster and more robust means of accessing your data. You can access all of your existing content also using the new repository domain. Existing email content is not changed, since the old repository domain is still supported.

The switch of the endpoint to the new repository domain is performed automatically as long as you have not configured a customer-managed CDN in the Content Repository Configuration app.
In the email editor provided in the Content Studio, you will see that the image URLs have been changed accordingly when you select an image from the Simple Content Repository. In this case the new image URL format looks similar to this: https://smc-content.s4hana.ondemand.com/smd-a1b2c3d4e/public/dl?shr=<share>&obj=<obj>.

If you have configured a customer-managed CDN in the Content Repository Configuration app, you are asked to perform a manual migration.
A new button “Migrate” is available for simple repository usage of the Content Repository Configuration app.


Screenshot Content Repository Configuration


To ensure that both image URL formats (old and new) work with your CDN(s), you have in principle the following options:

  1. Provide a new CDN distribution with the new repository domain as the endpoint (or origin). It is not necessary to adjust your old CDN configuration.

  2. Adapt your existing CDN configuration by replacing the old endpoint (or origin) with the new endpoint. Additionally add a logic to enable the accessibility of the images with the old image URL format.


Option 1:

This is the slightly easier option, because you do not modify your active CDN but add a second CDN with the new endpoint.
You can make the changes at any time and do not need an extra maintenance window because your active CDN is not affected.
The old image URL format will be served via the old repository domain and the new image URL format will be served via the new repository domain.
The disadvantage of this option is, that the performance and stability is only improved for completely new created email content but not for the existing content or copied content (considering email templates and reusable blocks!).
Furthermore you will have to maintain two CDN distributions in the future.

If you choose this option, you should perform the following steps:

  • In your CDN provider console, create a new CDN distribution with similar settings to your active CDN (e. g. enable caching of URL parameters), but with the endpoint to the new repository domain smc-content.s4hana.ondemand.com.

  • Deploy your changes in the CDN provider console.

  • In your web browser test some image URLs with the new image URL format pointing to your new CDN domain you created.
    The new image URL format looks similar to this: https://<your CDN domain>/smd-a1b2c3d4e/public/dl?shr=<share>&obj=<object>. The path to your personal repository e. g. '/smd-a1b2c3d4e' can be seen in the field repository CDN in the Content Repository Configuration app. The values for the URL parameters can be taken from some existing images in the repository.

  • In the Content Repository Configuration app with the simple content repository usage, enter your new CDN domain in the field Domain Name in the section Domain Configuration and choose “Save”. Note: the change is effective immediately!

  • In the Content Repository Configuration app with the simple content repository usage, choose “Migrate” to confirm the change.

  • In the email editor of the Content Studio app, test some new emails created that contain images. The existing content will continue to work, as the old repository domain will not be changed.


Option 2:

This is the option we recommend at SAP. It is slightly more complex but has the advantage, that not only new email content but also existing content and copied content (considering email templates and reusable blocks!) will be improved in regards to performance and stability.
Additionally you only need to maintain one CDN distribution in the future.
We recommend performing the switch of the endpoint during a maintenance window, because it might affect the active functionality of your CDN!

If you choose this option, you should perform the following steps:

  • In your CDN provider console, change your existing CDN settings by replacing the old endpoint (e. g. smd-a1b2c3d4e.hana.ondemand.com) with the endpoint to the new repository domain smc-content.s4hana.ondemand.com.
    This will serve the incoming requests having the new image URL format.
    Remember to enable the caching of URL parameters, as it is not as it is usually not the default setting!

  • In your CDN provider console, add a logic (or behaviour) to adapt the URL of the incoming requests. If an incoming request URL contains the string '/mcm/' in the path (old URL format), this string must be replaced with the path to your personal repository e. g. '/smd-a1b2c3d4e/' (new URL format). The path can also be seen in the field repository CDN in the Content Repository Configuration app.

  • Deploy your changes in the CDN provider console.
    Note: the change is effective immediately once you deployed the settings!

  • In the Content Repository Configuration app with the simple content repository usage, choose “Migrate” to confirm the change.

  • In the email editor provided in the Content Studio app, test some existing and new email content created containing images.


Related information
Administration Guide: Configure Content Repositories
Integration Guide: Integrate with SAP Document Center
Blog post: Enabling an Out-of-the-box (Simple Content) Repository for Storing Images in SAP Marketing Cloud

If you have performed the migration to the new repository domain, please let us know your feedback!
8 Comments