Configuring TLS ports for Sametime Meeting Server

Determine the TLS ports for each IBM® Sametime® Meeting Server component and then update configuration keys to match in the Sametime System Console.

About this task

For every Sametime Meeting Server in your deployment, determine the port used for TLS communications; then log into the Sametime System Console create configuration keys for each of those ports.

Procedure

  1. Determine the TLS ports used by all Meeting Server components.
    1. On the deployment manager, log in to the WebSphere® Integrated Solutions Console as the WebSphere administrator.
      • Base Meeting Server: the deployment manager is the Sametime System Console: https://SSC_Host_Name:8701/ibm/console
      • Capture Server, Render Server, Conversion Server: the deployment manager is hosted on the server: https://https://Server_Host_Name:9043/ibm/console
    2. Open the WebSphere application servers page.
      • Base Meeting Server: Servers > WebSphere application servers
      • Capture Server, Render Server, Conversion Server: Servers > Server Types > WebSphere application servers
    3. In the "Communications" section, click Ports.
    4. Record the following ports:
      Be sure to note the name of the server whose ports are listed below, because you must record the ports for all Meeting Server components.
      • All servers: record the WC_defaulthost_secure port.
      • Base Meeting Server nodes in a cluster: record the PROXY_HTTPS_ADDRESS port for each of the WebSphere proxy servers that are deployed for the cluster.
      • Sametime Proxy Server: If your deployment includes Sametime Proxy Server, record its WC_defaulthost_secure port.
    5. Repeat this step for every Meeting Server component (Base Meeting Server, Capture Server, Render Server, and Conversion Server).
  2. On the Sametime System Console, log in to the WebSphere Integrated Solutions Console as the WebSphere administrator.
  3. Click Sametime System Console > Sametime Servers > Sametime Meeting Servers.
  4. For each Meeting Server component, set up configuration keys to support the use of TLS.
    1. In the list of Meeting Server components, click the link that represents the component you want to configure.
    2. Create a configuration key to enable TLS for the current component:
      1. Click New.
      2. Provide the Configuration Key name: meeting.recording.tlsVersion.
      3. Provide the Value: TLSv1.2.
      4. Click OK.
    3. For the same component, edit the following configuration keys to ensure that they match the values shown in the following list.
      Note: Depending on your Sametime deployment, some of the configuration keys in the list might exist on some Meeting Server components but not on others.

      In each configuration key, replace Port with the port number that you looked up for the component in Step 1.

      • docshare.remote.url = https://Conversion_Server_Host_Name:Port /DocumentShare/docshare
      • docshare.client.url = https://Base_Server_Host_Name:Port
      • meetingroomcenter.stProxySSLAddress = https://STProxyServer_Host_Name:Port
      • recording.api.remote.url = https://Capture_Server_Host_Name:Port
      • recording.capture.serverAddress = https://Capture_Server_Host_Name:Port
      • recording.render.serverAddress = https://Render_Server_Host_Name:Port
      • recording.capture.meetingServerAddress = https://Base_Server_Host_Name: Port
    4. Click OK.
    5. Repeat this step for every Meeting Server component in the list.