Configuring Sametime Community Server connectivityAdded by IBM on November 23, 2011 | Version 1 (Original)
|Define the host names and ports for Community Services on the IBM® Sametime® Community Server.
Define the host names and ports for Community Services on the IBM
® Community Server.
About this task
Community Services supports all presence (or awareness) and text chat activity in a Sametime
community. Any Sametime
client that contains a presence list must connect to Community Services on the Sametime
Community Services includes:
- Client login requests
- Connections from clients that access the Sametime server through a direct TCP/IP connection, or a HTTP, HTTPS, or SOCKS proxy server. Community Services clients connect to the Community Services multiplexer component, which is deployed on a separate machine from the Sametime Community Server.
- Directory access for user name search and display.
- Directory access to compile lists of all servers and users in the community.
- Dissemination of presence and chat data to all users connected to Community Services.
- Maintenance of privacy information for online users.
- Connections from the Community Services on other Sametime Community servers when multiple servers are installed.
- Logging of server community events to the Sametime log (stlog.nsf).
This must be completed separately for each server within a Sametime
Community Server cluster.
- 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 Connectivity tab.
- Under Server Connections, type the fully qualified Host Name and Port for the internal Sametime processes to communicate with one another.
Community Services listens for direct TCP/IP connections from Community Services of other Sametime Community Servers on this port. If you have installed multiple Sametime servers, this port must be open for presence, chat, and other data to pass between the servers.
- Under Client Connections, type the fully qualified Host Name and Port from which Community Services listen for direct TCP/IP connections and HTTP-tunneled connections from the Community Services clients.
A direct TCP/IP connection occurs when the Sametime client uses a unique Sametime protocol over TCP/IP to establish a connection with the Community Services.
- Under HTTP Tunneled Client Connections, type the fully qualified Host Name and Port from which Community Services clients can make HTTP-tunneled connections to the Community Services multiplexer.
Community Services clients can make HTTP-tunneled connections on both ports 80 and 8082 by default. Port 8082 ensures compatibility with previous Sametime releases. In previous releases, Sametime clients made HTTP-tunneled connections to the Community Services only on port 8082. If a Sametime Connect client from a previous Sametime release attempts an HTTP-tunneled connection to a Sametime server, the client might attempt this connection on port 8082.
- If you will be using previous version of the Sametime Meeting Room client, click Enable pre 8.5 releases of the Meeting Room client to try HTTP Tunneling to the Community Server after trying other options.
- Under HTTPS Tunneled Client Connections, type the fully qualified Host Name and Port from which the Community Services clients attempt HTTPS connections when accessing the Sametime Community Server through an HTTPS proxy server.
If a Community Services client connects to the Sametime Community server using HTTPS, the HTTPS connection method is used, but the data passed on this connection is not encrypted.
- Click OK.
- Restart the Sametime Community Server for settings to take effect.
What to do next
Configuring LDAP and Domino connections
Parent topic: Installing a Sametime Community Server and supporting software
Previous topic: Clustering Sametime Community Servers
Next topic: Configuring LDAP and Domino connections