HCL Content Composer

The HCL Content Composer manages Digital Experience site content.

Users can access the Content Composer features in HCL WebSphere Portal 9.5 Container Update CF_181 and higher releases.

Follow the instructions below to configure the HCL WebSphere Portal 9.5 Content Composer.

Limitations

The following limitations exist in HCL Content Composer:

• Content created using Content Composer and Digital Asset Management cannot be used with the HCL WebSphere Portal Projects capabilities.

• Content Composer and Digital Asset Management may not be used with HCL DX 9.5 container deployments that set an alternate context root.

• The use of Content Composer and Digital Asset Management features in a Virtual Portal deployment pattern are not yet supported.

• Content Composer Workflow selections can be established in a content template and workflow stages in content items can be progressed by the content author. Workflow item comments and content item workflow approvals by designated reviewers will be introduced in a later update.

• When planning to use the Content Composer features in an authoring environment, with the Container Update CF_181 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 uploading a file or an image via Experience API or Content Composer, the actual file uploaded may be larger than expected when processing through Experience API or Content Composer. This is because REST data in Experience API must be text-based, which is why when uploading files via Experience API or Content Composer, Base64 is used to convert binary content before sending it to HCL WebSphere Portal. The size increase caused by the Base64 transformation causes the encoded file or image to be approximately 30% larger than the file size on disk.

• In Content Composer, there would be a slight delay of the items from an imported library to be accessed. It is advised to do cache invalidation.There are two ways to do a cache invalidation:

  1. On a Kubernetes platform, HCL recommends used authoring for any kind of content editing; or

  2. Use the IBM Extended Cache Monitor for IBM WebSphere Application Server.

     • IBM Extended Cache Monitor for IBM WebSphere Application Server technology preview

• HCL Content Composer 9.5 CF191 and higher releases supports the following Content Elements only:
  • Text elements
  • Media elements (File and Image)
  • Date and Time elements
  • Component Reference elements
  • Link elements
  • Option Selection elements
  • User Selection elements

See:

• Install HCL WebSphere Portal 9.5 Components
• Configure access to HCL Content Composer
• The HCL Content Composer Dashboard
• Content versioning
• Search content in HCL Content Composer
• Author and manage content items using HCL Content Composer
• Author and manage content templates using HCL Content Composer