Registering a Sametime Meeting Server on IBM i with the Sametime System Console

After installing an IBM® Sametime® Proxy Server or Sametime Meeting Server on IBM i without a Sametime System Console deployment plan, register it with the Sametime System Console to allow you to manage all Sametime servers from a central location. If you are registering a Proxy Server or Meeting Server primary node (PN), you must federate the PN into an existing cell during registration.

Before you begin

Important: This procedure is only required when you install a Sametime Proxy Server or Sametime Meeting Server without a Sametime System Console deployment plan.

Before you register the server, verify that you have completed the following tasks.

Sametime Community Server

  • The Community Server must be configured to use an LDAP directory.
  • The Community Server must be started.
  • The Sametime System Console must be started.
  • The LDAP server must be started.
  • The LDAP server must be connected to the Sametime System Console.

Sametime Proxy Server

  • The Sametime System Console must be started.
  • The Community Server that the Proxy Server connects to must be registered with the Sametime System Console.
  • The Sametime Proxy Server database (STPROXY) must be connected to the Sametime System Console.
  • When you are registering a primary node and adding it to a cell, both the primary node and the deployment manager for the cell must be started.

Sametime Meeting Server

  • The Sametime System Console must be started.
  • The LDAP server must be started.
  • The LDAP server must be connected to the Sametime System Console.
  • The Meeting Server database (MTG) must be connected to the Sametime System Console.
  • When you are registering a primary node and adding it to a cell, both the primary node and the deployment manager for the cell must be started.

About this task

Working from the Sametime server that you want to connect with the console, follow these steps to update properties files and run the registration utility to register the server with the console.

During this task you will edit the following files; click the topic titles to see details on each file. Use Ctrl+Click to open the topic in a new browser tab or window so you can keep it open for reference:

Procedure

  1. On the Sametime server you plan to register, navigate to the console directory.
    • Community Server

      The console directory is a subdirectory of the Sametime Community Server data directory.

    • Proxy Server
       /QIBM/ProdData/WebSphere/Appserver/STPServerinstall_type/console

      The install_type indicates the type of server profile you installed. For example,

      /QIBM/ProdData/WebSphere/Appserver/STPServerPN/console

    • Meeting Server
       /QIBM/ProdData/WebSphere/Appserver/STMServerinstall_type/console

      The install_type indicates the type of server profile you installed. For example,

      /QIBM/ProdData/WebSphere/Appserver/STMServerPN/console

  2. In the console directory, make backup copies with different names of the console.properties and productConfig.properties files.
  3. Update the following values in the console.properties file and save the file.
    Table 1. console.properties settings
    Property Value
    SSCHostName Provide the fully qualified host name of the Sametime System Console server.
    SSCHTTPPort Specify the HTTP port used for the Sametime System Console server if SSL is not enabled and the value for SSCSSLEnabled is "false."

    To determine the correct HTTP port, open the AboutThisProfile.txt file for the Sametime System Console Application Server Profile and use the setting specified for the "HTTP transport port." The default profile name is STSCAppProfile.

    On IBM i, look for the AboutThisProfile.txt file in the following location: /QIBM/UserData/Websphere/AppServer/version_number/SametimeWAS/profiles/STSCAppProfile/logs/AboutThisProfile.txt
    SSCUserName Enter the IBM WebSphere Application Server User ID that you created when you installed Sametime System Console. The default is wasadmin.
    SSCPassword Enter the WebSphere Application Server password associated with the SSCUserName.
    SSCSSLEnabled Change this value to "true" to connect to the Sametime System Console using a secure connection.
    SSCHTTPSPort Specify the HTTPS port used by the Sametime System Console server if SSCSSLEnabled is set to "true."
  4. Update the productConfig.properties file with the values needed for the server you are registering. Then save the file.
    Required values not listed are filled in automatically.
    • Sametime Community Server

      • DepName: Provide a descriptive name for your deployment. It must be a unique deployment name on the Sametime System Console.

    • Sametime Proxy Server
      • DBAppPassword: Specify the password associated with the database ID.
      • WASPassword: Specify the password associated with the WASUserID.
      If you are registering a primary node, you must specify additional values for the cell where the node will be added:
      • WASDMHost: Specify the fully qualified hostname of the deployment manager for the cell.
      • WASDMSoapPort: Specify the soap port of the deployment manager for the cell.
    • Sametime Meeting Server
      • DBAppPassword: Specify the password associated with the database ID.
      • WASPassword: Specify the password associated with the WASUserID.
      • LDAPBindPwd: Specify the password associated with the LDAPBindDN.
      If you are registering a primary node, you must specify additional values for the cell where the node will be added:
      • WASDMHost: Specify the fully qualified hostname of the deployment manager for the cell.
      • WASDMSoapPort: Specify the soap port of the deployment manager for the cell.
  5. If you are registering a Sametime Community Server, start the server. Otherwise, proceed to the next step.
  6. From an IBM i command line, run the following command to start the QShell Interpreter:

    QSH

  7. Run the cd shell command, specifying the fully qualified path to the console directory you used in Step 1.
  8. Run the appropriate shell script to register the server:
    • Sametime Community Server

      registerSTServerNode.sh

      When prompted, specify the following information:
      • Full path to the Sametime Community Server data directory where the notes.ini file is located.
      • The Community Server Administrator ID and password.
    • Sametime Proxy Server

      registerProduct.sh

      If registering a primary node, run the following command:

      registerProduct.sh -federateNode
    • Sametime Meeting Server

      registerProduct.sh

      If registering a primary node, run the following command:

      registerProduct.sh -federateNode
  9. When the registration script completes, press F3 to exit QSH.