Many meeting-related 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 client preferences to automatically update client
preferences with the Expeditor managed settings framework.
Procedure
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:
- com.ibm.rtc.meetings.shelf/serverName
Use the fully qualified
domain name of the Meeting Server.
- com.ibm.rtc.meetings.shelf/connectionType
The default of 0 uses
a direct connection. Specify 1 to use a reverse proxy server.
- com.ibm.rtc.meetings.shelf/serverPort
Specify the port used
to connect to the Meeting Server.
- com.ibm.rtc.meetings.shelf/useHTTP or com.ibm.rtc.meetings.shelf/useHTTPS
- com.ibm.rtc.meetings.shelf/useHTTP: Set this to true to
force the client to use HTTP when connecting to the Meeting Server.
- com.ibm.rtc.meetings.shelf/useHTTPS: Set this to true to
force the client to use HTTPS (a secure connection) when connecting
to the Meeting Server.
- 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 CommunityServer to log in to a Meeting Server without
being challenged, set the following keys:
- com.ibm.rtc.meetings.shelf/useCommunityCredentials=true
- com.ibm.rtc.meetings.shelf/communityServerName=server_namewhere server_name matches
the community server name that is configured in the client.
- com.ibm.rtc.meetings.shelf/loginByToken=true
If the Community
Server and Meeting Server are configured in the same single sign-on
domain, setting this key 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 when logging
in to a Meeting Server, set the following key:
com.ibm.rtc.meetings.shelf/useCustomCredentials=true
- (Optional) To prevent users from modifying their Meeting
Server lists, set the following keys: