Sametime Awareness in HCL Connections

HCL Sametime Sametime Forum
1

Hi Community members,

Don't know if it is the right forum (between Connections or Sametime).

ST12 premium is setup (docker) runs fine with Notes/iNotes/Verse, but i've changed the fqdn and seems it impacts Sametime Awareness in HCL Connections.

HCL Connections side, I've updated (wsadmin + checkin +chckout, deleted temp and wstemp folders) LotusConnections-config.xml with the new FQDN (without the :8443 port), but homepage still connect to the old FQDN on port 8443.

I do know the admin has customized in the past Connections 7, but no customization is defined anymore, I do suspect a file still referencing the old sametime proxy FQDN, but I can hardly find it (event tried on the whole server: find / -type f -exec grep -l "oldfqdn.company.com:8443" {} \;) witout success.

Next step will be to use CONNECTIONS_CUSTOMIZATION_DEBUG=true in WAS to see what really happens, but well.....

So if you do have any hint.... I'll take it

2

Hi Jerome,

My name is Tony, and I'm with the HCL Connections Support Team.

If you haven't done so already, I suggest that you generate and propagate the web server plugin.

Tony Dezanet
HCL Connections Support

3

Thx Anthony, I always forget this!

4

Hi Jerome,

If you are using Sametime 12, by default you do not get an LTPA token, which is what we need for integration with Connections.

You need to export your LTPA keys from WebSphere/Connections (take note of the password), then do this on Docker:

Community-Pasted-Attachment-1654727511152.png599×177 10.1 KB

Thanks!

Casey

5

Hi Casey,

Yes I've done it when I was at Engage, works fine, thanks. The actual problem was that the old fqdn was still used into connections home page and other zones, just doing a propagate the plugin config file was ok after the LotusConnections-config.xml and proxy.tpl were updated.