Why is this so important to mention and create a blog about it?
The ST_COMMUNITY_ID parameter, in sametime.ini, is used for connecting your Contactlist to one or more Sametime Community servers. Until Sametime V9 you could create a Sametime cluster and connect several servers to each other. The procedure tells me to set the ST_COMMUNITY_ID parameter to all these servers to the same value. When you failover to another server, your Contactlist will survive.
When you only have 1 Sametime server, the documentation tells me to leave this parameter empty. When Sametime starts, and the parameter is empty, the documentation tells me that Sametime fills it with the hostname of the server.
See article: https://help.hcl-software.com/sametime/11.6/admin/config_chat_set_id.html
All users and public groups in the contact list are associated with a specific community. Each community is defined by a community name that is configured by the ST_COMMUNITY_ID flag in the [Config] section of the sametime.ini file. When the flag is not set, the default value is the server host name (a specific Sametime® node that user the logs into).
But …… when migrating from Sametime v9 to Sametime V12 and with the ST_COMMUNITY_ID emtpy on both ends, we discovered some problems with the migrated Contactlists. When a users logs in, into the new Sametime V12.0.3 server, the Contactlist was empty. Even when we set the ST_COMMUNITY_ID as the old servers’ hostname.
Details for the environments:
Old situation Sametime V9:
- URL: sametime.domain.local (CNAME in DNS)
- Hostname: srvst01.domain.local
- Domino name: DOM-ST/ORG
New situation Sametime V12.0.3:
- URL: stchat.domain.local (CNAME in DNS)
- Hostname: srvchat01.domain.local
- Domino name: N/A
The documentation tells me that if ST_COMMUNITY_ID is empty, Sametime fills it with the hostname of the server, so it should be srvst01.domain.local on the old server and srvchat01.domain.local for the new server. But none of that is true.
Sametime 9: ST_COMMUNITY_ID seems to filled with the Sametime URL filled in on your Domino FQIN setting when it’s empty, in our case…. the CNAME.
Sametime 12: ST_COMMUNITY_ID seems to be filled with the public_url parameter when it’s empty.
The only solution when you migratie a Sametime server with an empty ST_COMMUNITY_ID is to also migrate the CNAME to the new server and use the CNAME as the public_url to connect to the new server.
Views: 21