Setup guide

IBM Lotus Sametime 7.5 Release Notes Installation, migration, upgrade, and configuration
Multiple Community considerations
The 7.5 Sametime Connect client supports the ability to define multiple Sametime communities in an
interface, and be logged into one or more of those communities at the same time. There are some
important points to consider if you need to define more than one community or switch from one
community to another:
z
If you have multiple communities in which some are 7.5 communities and some are pre-7.5
communities, you should define your primary community (the main community defined first when
the client is first run) as your most used 7.5 community.
z
Some features in 7.5 work only with your primary community and require policies to be enabled
for them, for example, voice chat and telephony. You will not be able to voice chat or participate
in telephony calls with users of a community that is not defined as your primary community.
z
Selective 'Do Not Disturb' requires a 7.5 server, and will only work with users from your primary
community
New UNIX config values not always propagated by single restart
At a high level, configuration values on a Sametime server are provided to system components by a
configuration servlet. The values provided by this servlet are stored in a cache to improve performance.
When system components retrieve values, these values come from the cache.
If configuration changes are made directly to a data source, such as STConfig.nsf or sametime.ini, the
server must be restarted. On Windows, as the server comes up, the config cache is refreshed from the
config servlet before system components can retrieve values from the cache.
On UNIX, however, the order of component startup is more random than on Windows. As a result, it's
possible that system components will retrieve configuration values from the cache before it gets
refreshed. As a result, the refresh of the cache occurs after values have already been retrieved. If this
happens, a second restart of the server will guarantee that system components retrieve the freshest
configuration values.
There are a couple of other methods for changing configuration values that should assure retrieval of the
latest values:
1. Make the configuration changes.
2 Stop the server.
3. Delete the file 'SametimeCommunity2.xml' from the data directory.
4. Restart the server.
Or method:
1. Make the configuration changes.
2. In the Domino console, restart the HTTP server with the command 'tell http restart'.
3. Wait a few moments for Domino to respond that the HTTP server has restarted.
4. Restart the entire server.
Either of these methods should cause sytem components to retrieve the latest configuration values.
24