HCL Digital Asset Management | HCL Digital Experience

HCL Digital Asset Management (DAM) delivers a central platform to store and include rich media assets in Digital Experience site content to present engaging, consistently branded experiences across digital channels.

Users can access the HCL Digital Asset Management features in HCL Digital Experience 9.5 Container Update Release CF181 and higher releases.

Follow the instructions below to install, configure, and use the HCL Digital Experience 9.5 Digital Asset Management features.

Notes: The following limitations exist in HCL Digital Asset Management:
  • Content created using Content Composer and Digital Asset Management cannot be used with the HCL Digital Experience Projects capabilities.
  • Deployments that set an alternate context root are supported in Content Composer from HCL DX 9.5 Container Update CF195 and in DAM from HCL DX 9.5 Container Update CF193.
  • Renditions for graphics interchange format (GIF) images are not yet supported.
  • When planning to use the Content Composer features in an authoring environment, with the Container Update CF181 release, it is only supported when running with one Digital Experience 9.5 core container (pod). This limitation does not apply when using the Web Content Management Authoring Portlet or when just using the new Digital Asset Management feature. It also does not apply to environments used for rendering.
  • When using Kaltura with Digital Asset Management, all uploaded videos are anonymously accessible for everyone who knows the URL, regardless of the access control setting on the collection containing the video. Do not use Kaltura integration if you have sensitive videos that should not be available without authentication.
  • If you are using a content delivery network (CDN) such as Akamai, using Vary: Origin may prevent you from caching content. To bypass this limitation, your CDN configuration must strip the Vary header on the way in, to reinstate your ability to cache content. On the way out, you can append the Origin parameter to the Vary header when serving a response using 'Modify Outgoing Response Header'.