Managing general community servicesAdded by IBM on November 23, 2011 | Version 1 (Original)
|The general community services settings control the interaction of the IBM® Sametime Community Server with an LDAP directory and the maximum number of users allowed on the server.
The general community services settings control the interaction of the IBM
® Sametime Community Server with an LDAP directory and the maximum number of users allowed on the server.
About this task
These settings must be addressed for each server within a Sametime Community Server cluster.
Parent topic: Managing community services
- Log in to the Integrated Solutions Console.
- Click Sametime System Console -> Sametime Servers -> Sametime Community Servers.
- In the Sametime Community Servers list, click the deployment name of the server with the connectivity information that you want to change.
- Click the Community Services tab.
- Use the following table to set general server-wide settings for users of the Sametime Community Server.
Table 1. Server-wide settings
|Number of entries on each page in dialog boxes that show names in the directory||Controls the number of user and group names that display when a user browses the directory. When an user browses the names and groups in the directory, the directory entries (names and groups) are listed on "pages" in a dialog box. The default is 100 entries per page. It is best to use a setting between 100 and 200 entries. Higher settings cause more data to be transmitted on the network when a user browses the directory.|
|How often to poll for new names added to the Sametime community directory (minutes)||Controls how frequently the cache of user names is updated with new information from the directory. The Sametime Community Server maintains a cache that contains information about the users and groups in the community. This cache must be or refreshed periodically to ensure that users who have recently been added to a directory can be displayed in the presence lists of all Sametime clients. The update occurs only if changes are made to the directory during the update interval. The default setting is 60 minutes.|
|How often to poll for new servers added to the Sametime community (minutes)||Controls the time interval in which the Sametime® Community Server receives an updated list of all Sametime servers. If you have deployed more than one Sametime Community Server, the community services on each server must maintain a list of all other Sametime Community Servers in the Sametime community. Community services uses this list to ensure that users who have different home servers or different home clusters can see each other in presence lists and communicate through instant messaging and chat. The default setting is 60 minutes.|
|Maximum user and server connections to the community server||Controls the maximum number of connections allowed to Sametime Community Server. The connections include both client connections and server-to-server connections. A client connection occurs when a user starts the Sametime client. Server-to-server connections occur when you have deployed multiple Sametime Community Servers and different home servers are specified for users. The limit is 20,000 connections.|
|Select the authentication type that users can use while logging into the Community server:
- LTPA or Sametime token
- LTPA only
|Controls the authentication type. When LTPA or Sametime Tokens option is selected, the Sametime Community Server accepts authentication tokens generated by both Single-Sign On (SSO) and the Secrets and Tokens databases on the Sametime Community Server. This option is selected by default. When LTPA only is selected, selected, the Sametime Community Server accepts authentication tokens generated only by SSO (LTPA tokens).|
- Click OK.
- Restart the Sametime Community Server for settings to take effect.