Registering the updated Sametime Gateway server or cluster with the System Console

If the server being updated was previously registered with the Sametime®, you must run the registration utility again.

Before you begin

You must update the Sametime System Console to FP1 before attempting to register an FP1 server with it.

Procedure

Register the Gateway server with the System Console. In a cluster, be sure to register the deployment manager as well as all nodes.
  1. Set the upgraded server's deployment status to "upgrade".
    1. Log on to the server where the Sametime System Console is installed.
    2. Open a command window and run the following commands to set the deployment manager, the primary node, and (if you are upgrading a cluster) the secondary node:
      Note: In the following command, GWDM, GWPN, and GWSN are examples of Gateway deployment plan names.
      update ssc.deployment set depstatus='4614' where depname='GWDM'
      update ssc.deployment set depstatus='4614' where depname='GWPN'
      update ssc.deployment set depstatus='4614' where depname='GWSN'
  2. Collect information from the deployment manager's log.
    1. On the deployment manager for the Sametime Gateway server or cluster, change to the profile directory of the upgraded Gateway server:
      • Linux™: /opt/IBM/WebSphere/AppServer/profiles/GW_Profile/logs/RTCGWServer
      • Windows™: C:\Program files\IBM\WebSphere\AppServer\profiles\GW_Profile\logs\RTCGWServer

      Open the SystemOut.log file and note the Version and ID values.

  3. On the upgraded Sametime Gateway server, change to the STgateway/console directory located in the WebSphere® directory:
    • Linux: /opt/IBM/WebSphere/STgateway/console
    • Windows: C:\Program files\IBM\WebSphere\STgateway\console
  4. Prepare the productConfig.properties file by completing the following steps:
    1. Open the productConfig.properties file for editing.
    2. Update the OfferingVersion to the version you copied from the SystemOut.log file; for example: OfferingVersion=9.0.1.
    3. Update the ID to the ID you copied from the SystemOut.log file; for example: ID=20151130-0920
    4. Provide all passwords (they will be deleted automatically after you run the registration utility).
    5. Save and close the file.
  5. Prepare the console.properties file by completing the following steps:
    1. Open the console.properties file for editing.
    2. Verify that the settings for the Sametime System Console are correct.
    3. Provide all passwords (they will be deleted automatically after you run the registration utility).
    4. Save and close the file.
  6. Register the updated Sametime Gateway server with the Sametime System Console by running the following command:
    • Linux: sh registerProduct.sh –upgrade
    • Windows: registerProduct.bat -upgrade
  7. For a clustered deployment, you must additionally register the updated cluster by running the following command:

    Run this utility once only, after you have registered all of the individual servers.

    • Linux: sh registerProduct.sh –upgradeCluster
    • Windows: registerProduct.bat-upgradeCluster