Huddo Boards for HCL Connections CP¶
Deploying Huddo Boards into HCL Connections Component Pack (Kubernetes)
Prerequisites¶
- HCL Component Pack is installed and running
- WebSphere environment with Web Server (or another reverse proxy)
- kubectl is installed
- helm is installed
- SMTP gateway setup for email notifications if required
SSL / Network setup¶
Huddo Boards in Connections Component Pack (CP) uses the existing CP infrastructure.
The UI and API each require a unique route:
- UI for Boards:
[CONNECTIONS_URL]/boards. We will refer to this asBOARDS_URL - API Gateway:
[CONNECTIONS_URL]/api-boards. We will refer to this asAPI_URL
For more details on configuring an IBM HTTP WebServer as reverse proxy, please see here
Setup OAuth¶
You will need to setup an OAuth application with one (or more) of these providers for Huddo Boards to function. please refer to the following documentation:
| Provider | Registration / Documentation | Callback URL |
|---|---|---|
| HCL Connections (on premise) |
Huddo instructions | https://[CONNECTIONS_URL]/boards/auth/connections/callback |
| Microsoft Office 365 | Huddo instructions | https://[CONNECTIONS_URL]/boards/auth/msgraph/callback |
Configure kubectl¶
| Instructions | |
|---|---|
| Kubernetes | copy ~/kube/.config from the Kubernetes master server to the same location locally(backup any existing local config) |
Storage¶
S3¶
Huddo Boards for Component Pack deploys a Minio service. Please follow S3 storage details here to configure the NFS mount.
Mongo¶
Huddo Boards uses the Mongo database already deployed inside the Component Pack. There is no configuration required.
Licence Key¶
Huddo Boards / Activities Plus is a free entitlement however it requires a licence key from https://store.huddo.com. For more details see here.
Update Config file¶
Download our config file and update all the values inside. Descriptions as below.
Kubernetes variables:
| Key | Description |
|---|---|
global.env.APP_URI |
https://[BOARDS_URL] (e.g. https://connections.example.com/boards) |
webfront.ingress.hosts |
[CONNECTIONS_URL] (no protocol, e.g. connections.example.com) |
core.ingress.hosts |
[API_URL] (no protocol, e.g. connections.example.com/api-boards) |
minio.nfs.server |
IP address of the NFS Server file mount (e.g. 192.168.10.20) |
minio.storageClassName |
(Optional) name of the storage class when using dynamic provisioning |
Boards variables:
Are detailed here.
Customising Boards notifications:
Some elements of the Boards notifications that are sent out can be customised.
Activity migration variables:
The Activity migration chart will be deployed separately but use the same config file. The variables are described here.
Deploy Boards Helm Chart¶
Install the Boards services via our Helm chart
helm upgrade huddo-boards-cp https://docs.huddo.com/assets/config/kubernetes/huddo-boards-cp-1.1.1.tgz -i -f ./boards-cp.yaml --namespace connections --recreate-pods
Note:
--recreate-podsensures all images are up to date. This will cause downtime.
Add Proxy Config¶
Connections On Premise - update WAS config¶
in the linked document you should use the IP of your kubernetes manager and the http port for your ingress (32080 for default component pack installs)
Please follow these instructions
Integrations¶
HCL Connections¶
Microsoft Teams¶
Migrate Activities data¶
Please follow the instructions here