You can distribute updates to IBM
® client communities automatically using a managed-community-configs.xml
file. The managed-community-configs.xml
file is policy-based, so you can control communities for different user groups.
About this task
You can also use the managed-community-configs.xml
file to manage secondary communities, while preventing users from adding or deleting communities. Set the Allow Multiple Communities policy to false
and use the managed-community-configs.xml
to define the desired secondary communities. The client allows the user to log into secondary communities defined in the .xml file, but the user cannot delete secondary communities defined in the file.
At login time, the client receives policies and checks for the existence of a managed-community-configs.xml
file according to the Sametime update site URL
policy. For example, if the administration update site URL is http://example.com/updates
, the client looks for the file in http://example.com/updates/managed-community-configs.xml
Follow these steps to create and post a managed-community-configs.xml
- Create a settings XML file and save it as managed-community-configs.xml.
- Add settings for communities and actions in the file.
- Post the file to the policy-configured administration update site URL.
To test changes in the managed-community-configs.xml
file, create a policy set that includes the administration update site URL and place the .xml file in the location specified by the update site URL. Apply the policy to yourself and log in to the client to verify the expected changes take effect. You can also enable logging of the managed settings to help debug problems. To enable logging for the handling of the remote managed-community-configs.xml
file, set the following log level in the user.home/Lotus/Sametime/.config/rcpinstall.properties
What to do next
One additional step should be taken if you change the settings file to update the host name of a community to a new server that is part of the same community, meaning that users’ contact lists are still valid with the new host. You must set the ST_COMMUNITY_ID in the sametime.ini
file of both servers to the same value and ensure that all the communities in your cluster are using the same community ID. This will prevent duplicate communities from being created on the client when logging into the new host for the first time.
Parent topic: Configuring the Sametime client