Define the host names and ports for Community Services
on the IBM® Sametime® 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
Server. Community Services includes:
- Client login requests
- Connections from clients that access the Sametime server through
a direct TCP/IP connection, or an HTTP, HTTPS, or SOCKS proxy server.
Community Services clients connect to the Community Services multiplexer
component, which is deployed on a computer separate 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.
Procedure
- Log in to the Integrated Solutions Console.
- Click .
- 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.
- In the Server Connections section,
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.
- In the Client Connections section,
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.
- In the HTTP Tunneled Client Connections section,
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 client
from a previous Sametime release
attempts an HTTP-tunneled connection to a Sametime server, the client
might attempt this connection on port 8082.
- In the HTTPS Tunneled Client Connections section,
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.