HCL Sametime 11.6 and MongoDB 4.4 - how to enable mongo security correctly  

By Matteo Bisi | 6/14/21 1:53 AM | Infrastructure - Sametime | Added by Roberto Boccadoro

HCL Sametime 11.6 is supporting MongoDB 4.4 and this is the suggested version in case of new install. One of the suggested steps during a Community setup is enable the Mongo security as described here , but the steps there are not enough, because 4.4 version in case of replica set , require also the creation and the use of a shared key to every Mongo server involved in the replica set, even if the replica set is composed by 1 node.

How to install correctly Sametime Community over Domino 11.0.1 FP3 on linux  

By Matteo Bisi | 6/9/21 9:44 AM | Infrastructure - Sametime | Added by Roberto Boccadoro

During last weeks I'm working mostly on HCL Sametime preparing some meetings environments. After the release of the 11.6 we have noted the server wasn't able to start if installed after FP3 of Domino 11.0.1. The issue is similar to the Traveler issue , but we have fixed it in this way:

How to upgrade HCL Sametime Community and Proxy server 11.5 to 11.6  

By Ales Lichtenberg | 6/1/21 3:01 AM | Infrastructure - Sametime | Added by Oliver Busse

HCL Sametime server 11.6 was released. Official announcements will come soon. Register for this official launch event on June 7 Although the upgrade from version 11.5 is the same as previous release, I created a simple Step by Step tutorial.

HCL Sametime Meetings – Meeting Chat Issue  

By Milan Matejic | 5/17/21 5:20 AM | Infrastructure - Sametime | Added by Roberto Boccadoro

Recently I ran into the issue with HCL Sametime, the Chat was not working inside the Sametime Meetings. In this environment, the Sametime Meetings components are deployed on a single Docker host server. After a little bit of Troubleshooting and Log Analysis, I found the following error in the Sametime Proxy catalina logs: WARNING [https-jsse-nio-443-exec-8] com.ibm.rtc.stproxy.servlet.STProxyServlet.forward CLFRX0050E: User null – /stwebapi/chat/nway – <meeting_server_ip_address> is not authenticated.