Sametime Community ServerAdded by IBM on November 23, 2011 | Version 1 (Original)
|The Sametime Community Server runs on Lotus Domino. It supports all presence (or awareness) and text chat activity in a Sametime community. Any Sametime client that contains a presence list must connect to the Sametime® Community server.
The Sametime Community Server runs on Lotus Domino. It supports all presence (or awareness) and text chat activity in a Sametime community. Any Sametime client that contains a presence list must connect to the Sametime
® Community server.
Basic functionality supported by the server includes:
Parent topic: What is Sametime?
- Handling client login requests.
- Handling connections from clients that access the Sametime server through a direct TCP/IP connection, or through HTTP, HTTPS, or SOCKS proxy servers.
- Providing directory access for user name search and display purposes.
- Providing directory access to compile lists of all Sametime servers and users in the community.
- Dissemination of presence and chat data to all users connected to Community Services.
- Maintenance and storage of privacy information, user preference settings, and presence lists for online users.
- Handling connections from the Community Services on other Sametime servers when Using multiple non-clustered Sametime Community Servers. Server-to-server connections for the Sametime Community Server occur on default TCP/IP port 1516.
- Logging of server events to the General log settings (stlog.nsf).
- Enabling a name entry prompt to appear when the ACL settings of a Domino® database enabled with IBM Lotus® instant messaging technology allows anonymous access. This name entry prompt ensures that the presence list in the Sametime database can display a name for the user.
Stand-alone Community Server multiplexer
Every IBM Sametime
Community Server contains an integrated multiplexer ("mux") component that handles and maintains connections from Sametime
clients to the Community Server. You can also choose to install a stand-alone multiplexer and connect it to the Community Server. The Community Server multiplexer machine dedicates its system resources to handling client connections but does not perform other Community Server processing. Distributing the Community Server workload between multiple servers in this way enables the Community Server to handle a larger number of connections for users and to function more efficiently.