Skip to main content

 –

Configuring custom repository storage

Suggest edit Updated on September 21, 2021

For all cloud or on premise implementations you can enable repository storage with your existing S3 repositories (S3, Azure, or local file storage).

Before you begin: Make sure that the IP of the Content Delivery Network you want to use for repository storage is allowed to access the Pega Web Service, so that the Content Delivery Network can serve images from the Web Service.
  1. Configure the repository connection.
  2. In Dev Studio, configure the following Dynamic System Settings:
    • MarketingImageAssets/IsRepositoryStorageEnabled - Set to true.
    • MarketingImageAssets/CustomRepositoryName - Enter the name of the repository rule which points to your repository. This setting overwrites the value of the setting MarketingImageAssets/DefaultRepositoryName.
    • Optional: MarketingImageAssets/Folder - Enter the name of the folder where Pega Customer Decision Hub will store the image assets. This folder will be located inside the root folder defined in the repository rule. If you do not define a folder for the images, they will be stored directly in the repository root folder.
    • Optional: MarketingImageAssets/CustomBaseURL - Enter the URL of the Content Delivery Network which you configured, and update the MKTDefaultSecured content security policy rule to include CustomBaseURL under the Image-Source category in the Allowed Websites column. If you leave this setting blank, the images will be rendered directly from the Pega Web Service. This setting overwrites the value of the setting MarketingImageAssets/BaseURL.
  3. Optional: To modify the maximum file size allowed for images, edit the MarketingImageAssets/AllowedFileSize Dynamic System Setting.
  4. Optional: To allow image types other than .png, .jpg, .jpeg, .tiff, and .heif, save the data transform AllowedImageTypes to your application ruleset and add new types as required.
  5. Run the D_RepositorySettings data page with flush mode on, or clear the cache.
    Flushing the DSS settings is required to apply the changes made to the settings.
What to do next: If you replace an image in the repository with a new version, the cached image on the Content Delivery Network must be invalidated and replaced with the new version of the image. Cache invalidation is automatic in the Pega Cloud repository, but when using your own S3 repository, you must configure the invalidation logic, which should be applied on a DELETE event to clear the image cache. For more information, refer to the documentation of your S3 repository.
    • Next topic Configuring default repository storage for Pega Cloud deployments
    Did you find this content helpful? YesNo

    Have a question? Get answers now.

    Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

    Ready to crush complexity?

    Experience the benefits of Pega Community when you log in.

    We'd prefer it if you saw us at our best.

    Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us