Importing the Render Server's certificate to the Base Meeting Server

On the computer hosting the IBM® Sametime® Meetings Base Meeting Server, retrieve the SSL certificate from the Render Server and import it into the Base Meeting Server.

Procedure

  1. First, look up the Render Server's host and port information as follows:
    1. On the computer hosting the deployment manager for the Render Server component, log in to the WebSphere® Integrated Solutions Console as the WebSphere administrator.

      Access the console by opening a browser and navigating to the following address:

      https://Render_Server_Host_Name:9043/ibm/console
    2. In the navigation list, click Servers > WebSphere application servers.
    3. In the list of application servers, click STMeetingServer.
    4. On the Configuration tab, click Ports.
    5. In the Ports table, look for SIP_DEFAULTHOST_SECURE and note the port number; you will use it later in this task.
  2. Now use that information to import the Render Server's certificate to the Base Meeting Server as follows:
    1. On the computer hosting the Base Meeting Server, log in to the WebSphere Integrated Solutions Console as the WebSphere administrator.
      Typically, the Sametime System Console is the deployment manager for the Base Meeting Server, and the URL for the WebSphere console is:
      http://SSC_host_name:8700/ibm/console
      If you installed the Base Meeting Server in its own cell, then the deployment manager is hosted on the same server as the Base Meeting Server, so the URL is:
      http://Base_Meeting_Server_host_name:8500/ibm/console
    2. In the navigation list, click Security > SSL certificate and key management > Key stores and certificates.
    3. On the Key stores and certificates page, select NodeDefaultTrustStore.
    4. Click Signer certificates > Retrieve from port.
    5. On the Retrieve from port page, provide the Render Server's host name and port.
    6. Provide an alias for the Render Server's certificate.
    7. Click Retrieve signer information.
    8. Restart the Base Meeting Server.