Preconfiguring multiple Sametime Meeting Servers using managed preferencesAdded by IBM | Edited by Benjamin Gold on May 23, 2012 | Version 3 (Show original)
|Many Meeting preferences can be set automatically using the Expeditor managed settings framework. This topic describes what you must set up in advance to preconfigure client preferences for multiple Sametime® Meeting Servers.
Many Meeting preferences can be set automatically using the Expeditor managed settings framework. This topic describes what you must set up in advance to preconfigure client preferences for multiple Sametime
® Meeting Servers.
About this task
Add these required client preferences to automatically update client preferences with the Expeditor managed settings framework.
Follow these steps to add the required entries for configuring managed preferences. You can set the preferences from the Notes
® configuration documents or in a managed-settings.xml file.
Decide on a unique identifier, a GUID, for the server. It must be of the form, "stmsNNNNNNNNNNNNN", where the Ns are a unique number made of 13 digits, such as the current system time when the meeting server was defined.
Open the Managed Settings page in the Notes configuration document.
Add these required entries, inserting the predefined GUID and a semi-colon (;) before the key. For example:
Add an entry to identify the available meeting servers by their GUIDs. Use the key that matches the types of clients that are deployed. Use semi-colons to separate the server GUIDs.
Clients running releases 8.5.2 and later:
Clients running releases 8.5.1 and earlier:
Note: You must set this key before a client has been configured to any meeting server; otherwise the key will not be recognized.
Specify whether users can re-use the credentials used to log into a community server or if they must use custom credentials.
To set up single sign-on, where the client re-uses the credentials from a community server to log in to a meeting server, set these keys:
com.ibm.rtc.meetings.shelf/GUID;communityServerName=server_namewhere server_name matches the community server name that is configured in the client.
For clients prior to 8.5.2 that want to use an SSO token to login to the meeting server instead of the username and password used to log in to the community server, set this key:
If the community server and meeting server are configured in the same single sign-on domain, this key, when set to true, forces the meeting client to log in with the LTPA token from the community server. For 8.5.2 clients and beyond, if the meeting server is configured to re-use the community server credentials, the client automatically attempts to log in with a user name and LTPA token before falling back to a user name and password. Note that clients running releases earlier than 8.5.2 can also use an LTPA token but do not attempt to do so automatically and have no fallback mechanism. This value cannot be applied to specific meeting servers. Because it is a global setting for all servers, do not use this value if you have these older clients and some community servers and meetings servers that are not configured for single sign-on.
For more information, see Preparing servers running on WebSphere Application Server for single sign-on.
To set the client to use custom credentials to log in to a meeting server, set:
(Optional) Prevent users from modifying their meeting server lists:
Setting this key to false prevents user from removing meeting servers.
Setting this key to false prevents users from adding meeting servers.
Parent topic: Preconfiguring a Sametime Meeting Server using managed preferences
Automatically updating client preferences with the managed-settings.xml file