Client configuration files used for managing communities

Understand the role of client configuration files that manage communities of users connected to the HCL® Sametime® Community Server.

The following table lists the client configuration files that manage communities of users who connect to the Sametime Community Server.

Table 1. Client configuration file names, locations, and purposes
File Location Purpose
managed-community-configs.xml Web server Update, add and delete communities, and manage community configuration settings (such as host name and loginByToken) for the deployed user base. The file is policy-based, so you can define different sets of preferences for different users. This method applies to both the Sametime Connect Client and to the Sametime client embedded in Notes®.
managed-settings.xml Web server Update and control client preferences for the deployed user base. When you post this file to an update site, clients receive new or updated preferences automatically. The file is policy-based, so you can define different sets of preferences for different users. This method applies to both the Sametime Connect Client and to the Sametime client embedded in Notes.
Note: Do not add community settings to this file. Community settings must be added to the managed-community-configs.xml file described in the previous row. If you want to use community settings, you must use a managed-community-configs.xml file.
plugin_customization.ini Client computer Set initial eclipse preferences when client install kits are deployed to desktops or when a new user launches the product for the first time. These preferences can be overridden at runtime for the logged in user base using the managed-settings.xml file. This method only applies to installed Sametime Connect clients.

Community settings (such as loginAtStartup and host) can be entered here to prepopulate community settings for a first time user. After the user logs in, only the managed-community-configs.xml file can be used to change community settings.