Verifying a Sametime Base Meeting Server or Meeting Document Converter Server installation on IBM i

Log in to the IBM® Sametime® Base Meeting Server or the Sametime Meeting Document Converter Server on IBM i to verify that the installation was successful. Complete this verification procedure on each Sametime Base Meeting Server and Sametime Meeting Document Converter Server you install on IBM i.

About this task

Verify the installation by logging in to the appropriate Sametime Meeting Server and then try creating a new meeting room.

Procedure

  1. From a web browser, navigate to the Meeting Room Center by entering this URL:

    http://serverhostname.domain:port/stmeetings

    Replace serverhostname.domain:port with your server name and port number.

    For example,

    http://stmeet1.example.com:9080/stmeetings

    Note: By default, the IBM WebSphere® proxy server listens on port 80, and forwards to the Sametime Meeting Server on port 9080.
    Tip: To verify the port number being used by the application, log in to the console on the Sametime Meeting Server:
    1. Enter this URL, replacing serverhostname.domain with the fully qualified domain name of the server.
      http://serverhostname.domain:8600/ibm/console

      8600 is the default port when the proxy server is installed as a Cell Profile.

      For example,

      http://stmeet1.example.com:8600/ibm/console
    2. Enter the IBM WebSphere Application Server user ID and password that you created when you installed the server.
    3. Click Servers > WebSphere application servers > STMeetingServer > ports > WC_defaulthost to find the port number.

    You can also verify the HTTP port number being used by the Sametime Meeting Server by opening the AboutThisProfile.txt file for the Sametime Meeting Application Server Profile and use the setting specified for the HTTP transport port. The default profile name is short_host_name STMPNProfile1 when you use a deployment plan to install the server.

  2. (Base Meeting Server only) Verify that the new Base Meeting Server was successfully federated to its deployment manager.

    The deployment manager handles administration tasks for the cell to which the new server is federated. If the server was not successfully federated, you will encounter problems when you attempt to administer it; you will also be unable to create a WebSphere Network Deployment cluster. Avoid these problems by verifying that the federation was successful and completing federation manually if needed.

    1. On the new Sametime server, navigate to the following directory: install_root/profiles/profile_name/logs
    2. Open the addNode.log file and check for confirmation that the new node was successfully added to the cell's deployment manager.
    3. If the node was not federated successfully, open QShell and run the addNode command to complete the federation: 
      install_root/bin/addNode.sh -profileName profile_name dmgr_host dmgr_SOAP_port

      where:

      • dmgr_host is the fully qualified host name of the deployment manager (typically the Sametime System Console).
      • dmgr_SOAP_port is the SOAP port of the deployment manager.

        The SOAP port is 8879 by default; you can check the port value by opening the deployment manager's WebSphere Integrated Solutions Console and clicking System Administration > Deployment Manager Communications > Ports.

  3. Create a meeting room by completing the following steps:
    1. Click Log In and then enter your User name and Password to log in to the Meeting Center.
    2. Click New Meeting Room, then fill in the fields and click Save.
    3. The new meeting appears in the list of meetings that you own. To join that new meeting, click the Enter Meeting Room option that corresponds to the new meeting.