Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Needs Clarification
Workspace Sametime
Categories Chat
Created by Guest
Created on Nov 8, 2023

Separate Sametime community servers with their own MongoDB instance should connect over port 1516 with the Persistent chat feature.

Separate Sametime community servers with their own MongoDB instance should connect over port 1516 with the Persistent chat feature.

Currently, separate Sametime Communities connecting over port 1516, each with its own MongoDB instance is not a supported configuration for the Persistent Chat feature.

The Sametime Convomap service on 'communityA' Server would have an entirely different view of the data than what is on the 'communityB' Server.

What will/won't work will be dependent on which community server out of the 2 'owns' the conversation as that will be the side that puts/reads it from MongoDB.

While the other side of the community server does not have the data to display.



  • Attach files
  • Admin
    Trevor Tallackson
    Reply
    |
    Dec 1, 2023

    Are these Docker or Kubernetes installs? Are both servers in the same "community" and configured to use the same LDAP server? The results reported are a result of two separate servers using two separate MongoDB servers so services chat history. .

  • Guest
    Reply
    |
    Nov 30, 2023

    Can you explain, why you would like to have this capability? What are you trying to achieve?