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.
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.
- Create a unique identifier, a GUID, for the server. It
must be of the form, "stmsNNNNNNNNNNNNN", where the Ns comprise a
unique 13-digit number, such as the current system time when the Meeting
Server was defined. You can use any combination of digits that you
want to use.
For example: stms1938847293723
- 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:
com.ibm.rtc.meetings.shelf/stms1938847293723;meetings.serverName=meetings.example.com
- com.ibm.rtc.meetings.shelf/GUID;meetings.serverName=
Use
the fully qualified domain name of the Meeting Server.
- com.ibm.rtc.meetings.shelf/GUID;serverId=
Use
the predefined GUID for the Meeting Server.
- com.ibm.rtc.meetings.shelf/GUID;serverConnectionType=
The
default of 0 uses a direct connection. Specify 1 to use a reverse
proxy server.
- com.ibm.rtc.meetings.shelf/GUID;meetings.serverPort=
Specify
the port used to connect to the Meeting Server.
- com.ibm.rtc.meetings.shelf/GUID;meetings.HTTP
or com.ibm.rtc.meetings.shelf/GUID;meetings.useSSLforLogin
- com.ibm.rtc.meetings.shelf/GUID;meetings.HTTP:
Set this to true if the client uses HTTP to
connect to the Meeting Server.
- com.ibm.rtc.meetings.shelf/GUID;meetings.useSSLforLogin:
Set this to true to force the client to use
SSL (an HTTPS connection) to connect to the Meeting Server
- 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.
- 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 the following keys:
- com.ibm.rtc.meetings.shelf/useCommunityServer=true
- com.ibm.rtc.meetings.shelf/communityServerName=server_name where 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, 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:
com.ibm.rtc.meetings.shelf/useCustomCredentials=true
- (Optional) To prevent users from modifying their Meeting
Server lists: