Configuring Sametime Community Server connectivity

Review the host names and ports for Community Services on the HCL 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 include:
  • 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 username 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.


  1. Launch an HCL Notes or Administrator client.
  2. Click Open > Applications > Open an Application.
  3. In the server field, type the name of the Community server. In the filename field, enter “stconfig.nsf” then click Open.
  4. Open the document for “CommunityConnectivity”.
  5. To place in edit mode, double-click anywhere inside the document.

    Complete the fields:

    Field name Value
    HTTP Tunneling Host Name

    Optional: This feature allows the use of HTTP tunneling in the desktop clients. No need to change this unless you are enabling tunneling.

    To configure tunneling, enter the fully qualified hostname of the server.

    HTTP Tunneling Port Optional: For HTTP tunneling, use this to set the port (8082 by default). Port 80 is the only other valid port (requires additional configuration).
    Is HTTP Tunneling Supported? Optional: Feature to allow for HTTP tunneling on the desktop clients.
    Direct TCP Host Name Enter the fully qualified internet hostname of the Sametime server.
    Direct TCP Port This is the port number that the clients will use to connect to Sametime. The default is 1533.
    HTTPS Host Name Optional:This setting is used to configure HTTPS tunneled client 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.
    HTTPS Port Optional:This setting is used with the HTTPS Host Name field for HTTPS tunneled client connections with accessing the Community server through an HTTPS proxy server.
    Community Trusted IPs Required:Enter the IP addresses of any Sametime server component or Sametime server that is not a Community server, such as a Sametime standalone Mux or Sametime Proxy server. Separate the IP addresses with commas.
    VPMX_TLS_HOST *Optional:This setting allows you to encrypt the client connections to the Sametime Mux over TLS. Enter the fully qualified internet hostname of the server.
    VPMX_TLS_PORT *Optional:This is the port used when enabling encrypted client connections to the Sametime Mux.
    Note: *Enabling encryption requires additional configuration. Please see the security section of the help center for more details.
  6. Once the settings have been entered, click File > Save to save the document.
  7. Restart the Community server for the changes to take effect.