HCL Connections Widget Setup¶

Add Huddo widgets into HCL Connections on-premise environments.

There are two ways to surface Ideas and Wikis inside a Community:

Community Highlights is preferred

Community Highlights needs no wsadmin access and no Communities restart, and community owners add the widgets themselves per page. Use the Community Widgets below only if you are not running HCEC.

Community Highlights (HCEC)¶

Huddo Ideas and Wikis integrate with HCL Connections Engagement Center (HCEC, formerly XCC), so they can be added as widgets to a Highlights page.

Each app serves its own widget registration script:

Widget	Script
Huddo Ideas	`https://[HUDDO_URL]/ideas/widgets/connections/xcc-onprem.js`
Huddo Wikis	`https://[HUDDO_URL]/wikis/widgets/connections/xcc-onprem.js`

Where [HUDDO_URL] is your Huddo URL including the /huddo prefix — e.g. connections.example.com/huddo.

HCEC loads a single custom.js

HCEC accepts one custom.js per environment, so these are fragments to merge, not files to upload as-is. Each one chains any existing XCC.X.init, so concatenation order does not matter and they coexist with an existing Huddo Boards registration.

Download both scripts from your running deployment, e.g.

curl -O https://[HUDDO_URL]/ideas/widgets/connections/xcc-onprem.js
curl -O https://[HUDDO_URL]/wikis/widgets/connections/xcc-onprem.js

Set the base path in each file to match your deployment.

Near the top of each script is a single constant, shipped with the app's own base path:
```
const IDEAS_BASE = "/ideas";     // ideas/xcc-onprem.js
const WIKIS_BASE = "/wikis";     // wikis/xcc-onprem.js
```
On Component Pack the apps are served under the /huddo prefix, so change them to:
```
const IDEAS_BASE = "/huddo/ideas";
const WIKIS_BASE = "/huddo/wikis";
```
Danger

Skipping this step is the usual cause of an empty widget — the iframe requests /ideas/community/connections, which does not exist on a prefixed install.
Build custom.js by concatenating the fragments.
```
cat ideas-xcc-onprem.js wikis-xcc-onprem.js > custom.js
```
If you already run Huddo Boards, append them to the existing Boards custom.js instead of replacing it — see the Boards CEC setup.
Open the HCEC admin page
```
https://[CONNECTIONS_HOST]/xcc/main
```
Click Customize, Engagement Center Settings, expand Customization Files and click Upload File, then select your custom.js.

Note: you must have the admin role for the Customize button to appear. The file must be named custom.js.
To validate:
1. Open the Highlights application in a Community
2. Click Customize, Widgets, then Huddo Ideas or Huddo Wikis
3. The widget should render the community's Ideas or Wikis content

Each widget exposes a Title and Height setting in its HCEC editor. Height defaults to 600px.

Community Widgets¶

The original Communities widget mechanism. It requires wsadmin access to the Deployment Manager and a restart of the Communities application, and the widgets are then available to every community.

SSH to the WAS Deployment Manager

Start wsadmin

cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin
./wsadmin.sh -lang jython -user wasadmin -password <password-here>

Check out the widgets-config.xml file.

execfile("profilesAdmin.py")
ProfilesConfigService.checkOutWidgetConfig("/LCCheckedOut", AdminControl.getCell())

Edit the widgets-config.xml file.

Find the resource element with the type of community, e.g. <resource ... type="community" ... >, then under <widgets>, then within <definitions> add the following, replacing [HUDDO_URL] with your Huddo URL including the /huddo prefix — e.g. connections.example.com/huddo:

Ideas¶

<!-- Huddo Ideas -->
<widgetDef defId="HuddoIdeas" modes="view fullpage" url="{webresourcesSvcRef}/web/com.ibm.social.urliWidget.web.resources/widget/urlWidget.xml" themes="wpthemeNarrow wpthemeWide wpthemeBanner" uniqueInstance="true">
    <itemSet>
        <item name="resourceId" value="{resourceId}"/>
        <item name="width" value="100%"/>
        <item name="height" value="500px"/>
        <item name="url" value="https://[HUDDO_URL]/ideas/community/connections"/>
    </itemSet>
</widgetDef>
<!-- END Huddo Ideas -->

Wikis¶

<!-- Huddo Wikis -->
<widgetDef defId="HuddoWikis" modes="view fullpage" themes="wpthemeNarrow wpthemeWide wpthemeBanner" uniqueInstance="true" url="{webresourcesSvcRef}/web/com.ibm.social.urliWidget.web.resources/widget/urlWidget.xml">
    <itemSet>
        <item name="resourceId" value="{resourceId}"/>
        <item name="width" value="100%"/>
        <item name="height" value="500px"/>
        <item name="url" value="https://[HUDDO_URL]/wikis/community/connections"/>
    </itemSet>
</widgetDef>
<!-- END Huddo Wikis -->

Check in the widgets-config.xml file.

ProfilesConfigService.checkInWidgetConfig()

Restart the Communities application via the ISC
Tip

If widgets no longer load in Communities and you see errors in the browser console like:
```
The following error occurs when retrieving widgetProcess production.
com.ibm.jsse2.util.h: PKIX path building failed: com.ibm.security.cert.IBMCertPathBuilderException: unable to find valid certification path to requested target
```
then please ensure the Connections domain root certificate is trusted in the WebSphere ISC. This can be added using Retrieve from port under SSL certificate and key management > Key stores and certificates > CellDefaultTrustStore > Signer certificates
Optional. Install the extensions for Connections Customizer. This includes a fix for the Community Widget that enables attachments to be downloaded as well as multiple new integrations for Connections.