HCL Digital Solutions
During a troubleshooting session in Component Pack, I checked the Kubernetes events.
To install the Component Pack for HCL Connections 8, you need to create a Mongodb5 image. The image sources can be found in the HCL MongoDB repository , and the process for creating the image is documented in Installing MongoDB5 for Component Pack 8 . The process involves using Docker, so if you have it installed, you can follow the instructions provided.
Elasticsearch in HCL Connections Componentpack is secured with Searchguard and needs certificates to work properly. These certificates are generated by bootstrap during the initial container deployment with
These certificates are valid for 10 years (
chain_ca.pem) or 2 years (
elasticsearch*.pem) and stored in the Kubernetes secrets
elasticsearch-7-secret. So when your HCL Connections deployment is running for 2 years, the certficates stop working.
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.
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
The last years I had issues with application servers using large amount of CPU and even hanging application servers running the Tiny Spellchecking service. It ended with disabled spellchecking in the Tiny editors