Preconfiguring a single Sametime Meeting Server using managed preferencesAdded by IBM on November 23, 2011 | Version 1 (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 a single Sametime® Meeting Server.
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 a single Sametime
® Meeting Server.
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.
- Add these required entries:
Specify whether users can re-use the credentials used to log into a community server or if they must use custom credentials.
Use the fully qualified domain name of the meeting server.
The default of 0 uses a direct connection. Specify 1 to use a reverse proxy server.
Specify the port used to connect to the meeting server.
- com.ibm.rtc.meetings.shelf/useHTTP or com.ibm.rtc.meetings.shelf/useHTTPS
Set the value to true for one of these entries. If you set the first entry to true, the client uses HTTP to connect to the meeting server. If you set the second entry to true, the client uses an HTTPS connection.
(Optional) Prevent users from modifying their meeting server lists:
- 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:
matches the community server name that is configured in the client.
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. 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.1 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:
Parent topic: Preconfiguring a Sametime Meeting Server using managed preferences
Automatically updating client preferences with the managed-settings.xml file