Enable Preview for source files like html or css with IBM Docs Viewer

Last Update:

Author: Christoph Stoettner
Read in about 1 min · 163 words

Fountain pen and a notebook

Photo by Aaron Burden | Unsplash

IBM Docs Viewer can open source files with syntax highlighting. This feature is default disabled, but sometimes very useful.

You need to enable it with IBM Connections Gatekeeper.

Open Gatekeeper with https://your-connections-fqhn/connections/config

editor image 7e5b4698 42c1 41b8 8fd8 3384ce2fe4cc

Now search for FILEVIEWER_PREVIEW_TEXT and change the value to True.

editor image 38576940 5388 4dec 8bcb 6b68227d18fb

Now when you open an html (or other text file) from IBM Connections Files it will open a preview and after a short flickering of the document the source is highlighted.

editor image 85b47fdf 5c91 4d3c 866c 6516a98f1994

Without that setting you just see a message like “no preview available for this” and a download option:

editor image 35e7e787 8610 4943 8f5a 3cda24133efc

Gatekeeper settings can be set in real-time, so no restart of Connections is needed to enable or disable this feature. I tested the preview with html, js and css, but I think nearly everything with mime-type text is possible.

Update 2018-06-15

You need the admin role of the Common Application to access the gatekeeper!

Add a comment
There was an error sending your comment, please try again.
Thank you!
Your comment has been submitted and will be published once it has been approved.

Your email address will not be published. Required fields are marked with *

Suggested Reading
Card image cap

In late 2021 I had an HCL Connections environment starting swapping, because the AppCluster used more than 30 GB of memory.

The system has

  • two nodes
  • is installed with the medium-sized deployment option
  • About 7500 users with a high adoption rate, because Connections is also used as intranet
Last Update:
Read in about 5 min
Card image cap

Last week I played around with the HCL Connections documentation to backup Elasticsearch in the article Backup Elasticsearch Indices in Component Pack .

In the end I found that I couldn’t get the snapshot restored and that I have to run a command outside of my Kubernetes cluster to get a snapshot on a daily basis. That’s not what I want.

Created: Read in about 4 min
Card image cap

During a migration from Cognos Metrics to Elasticsearch Metrics, I had some issues with the index. So I wanted to create a backup of the already migrated data and start over from scratch.

The official documentation has an article on the topic: Backing up and restoring data for Elasticsearch-based components , but I had to slightly adjust the commands to get a successful snapshot.

Last Update:
Read in about 6 min