Registering and federating a Sametime Proxy Server, Media Manager, Meeting Server, or Sametime Advanced Server

If automatic registration and federation fails after installing from a deployment plan, you can manually register an IBM® Sametime® server with the Sametime System Console. This process also federates the node if it was not federated after installation.

Before you begin

Verify that the Deployment Manager, the Sametime System Console server, and the Sametime server that you are registering are running.

About this task

This procedure works for the following Sametime servers:
  • Sametime Proxy Server
  • Sametime Media Manager
  • Sametime Meeting Server
  • Sametime Advanced
During this task you will edit the following files; click the topic titles to see details on each file. You may want to open each topic in a new browser tab or window so you can keep it open for reference:

Procedure

  1. Back up the console.properties and productConfig.properties files:
    1. On the server to be registered, navigate to the InstallLocation/console directory.
    2. Make backup copies (using different names) of the console.properties and productConfig.properties files.
  2. 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.

    For example, on Windows™ the file is stored at: C:/IBM/WebSphere/AppServer/profiles/AppServerProfile/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."
  3. Verify that the following settings in the productConfig.properties file are correct. Modify them as needed before saving and closing the file. You will need to add the passwords.
    Table 2. Sametime Proxy Server productConfig.properties
    Property Value
    WASPassword Specify the password associated with the WASUserID.
    DepName Provide a descriptive name for your deployment. It must be a unique deployment name on the Sametime System Console.
    NodeHostName The fully qualified host name of the server.
    Table 3. Sametime Media Manager productConfig.properties
    Property Value
    WASPassword Specify the password associated with the WASUserID.
    DepName Provide a descriptive name for your deployment. It must be a unique deployment name on the Sametime System Console.
    NodeHostName The fully qualified host name of the server.
    Table 4. Sametime Meeting Server productConfig.properties
    Property Value
    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.
    DepName Provide a descriptive name for your deployment. It must be a unique deployment name on the Sametime System Console.
    NodeHostName The fully qualified host name of the server.
    Table 5. Sametime Advanced
    Property Value
    DBAppPassword Specify the password associated with the database ID.
    WASPassword Specify the password associated with the WASUserID.
    DepName Provide a descriptive name for your deployment. It must be a unique deployment name on the Sametime System Console.
    NodeHostName The fully qualified host name of the server.
  4. If you are registering a Sametime Meeting Server, start the server. Otherwise, proceed to the next step.
  5. Now register the server:
    1. Run the registerProduct.sh registration utility from the /console directory.
      • AIX®, Linux™: ./registerProduct.sh -federateNode
      • Windows: registerProduct.bat -federateNode

    The utility registers the server, generating a log file called ConsoleUtility.log and storing it in the console/logs directory. If the registration is successful, a console.pid file will be added.