Registering an upgraded Community Server with the System ConsoleAdded by IBM on November 23, 2011 | Version 1 (Original)
|After upgrading an IBM® Sametime server to a Sametime Community Server on IBM AIX®, Linux®, Oracle Solaris, or Microsoft® Windows®, register it with the Sametime System Console, so you can manage all of the Sametime servers from a central location. If you upgraded a cluster, you must register each individual server before registering the cluster.
After upgrading an IBM
® Sametime server to a Sametime Community Server on IBM AIX
®, Oracle Solaris, or Microsoft
®, register it with the Sametime System Console, so you can manage all of the Sametime servers from a central location. If you upgraded a cluster, you must register each individual server before registering the cluster.
Before you begin
Make sure the following servers are ready for the registration task:
- The upgraded Sametime Community Server must be configured to use an LDAP directory, and must be started.
- The Sametime System Console must be started.
- The LDAP server must be started, and must be connected to the Sametime System Console.
About this task
During this task you will edit the following files; click the topic titles below 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:
- If you enabled SSL encryption on the previous version of the Sametime server, complete these substeps on the upgraded server:
If SSL is not enabled, skip this step.
- Locate the directory where the SSL certificate is stored and note the path (for example, C:\server.cer).
- Navigate to the directory where Java™ is installed.
For example, on Microsoft Windows: C:\Lotus\Domino\JVM\bin.
- Open a command window and run the following command:
keytool -import -alias serverSSL -file "C:\server.cer" -keystore
../lib/security/cacerts -storepass changeit -noprompt
represents the path where the SSL certificate is stored.
- Back up the console.properties and productConfig.properties files:
- Navigate to the Community Server's Sametime console directory:
Make back-up copies (using different names) of the console.properties and productConfig.properties files.
- AIX, Linux, Solaris: The console directory is under the Community Server data directory; for example: /opt/IBM/domino85/notesdata/console
- Windows: The console directory is under the Domino® directory; for example: C:\Lotus\Domino\console
Update the following values in the console.properties file and save the file.
Table 1. console.properties settings
Verify that the settings in the productConfig.properties file are correct, modifying them as needed before saving and closing the file.
|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."|
Now register the server:
Only the required values in this file are listed here:
Table 2. productConfig.properties settings
|DepName||Provide a descriptive name for your deployment. It must be a unique deployment name on the Sametime System Console. |
|NodeHostName ||Provide the fully qualified host name for the Community Server that is being registered.|
- Run the registration utility with the following command:
Upgrading from 8.0.x and 7.5.1
- AIX, Linux, Solaris: registerSTServerNode.sh
- Windows: registerSTServerNode.bat
- As the registration utility runs, you will be prompted to enter the following information:
|Location of notes.ini file||This is the user name and password that you use to manage the upgraded Sametime Community Server from the Community Server Administration Tool. Type the full path to the directory containing the notes.ini file, and press Enter. For example, on Windows: C:\Lotus\Domino|
|Lotus Domino administrator user name||This is the account that you use to manage the upgraded Sametime Community Server from the Community Server Administration Tool. Type the Lotus Domino administrator's user name, and press Enter.|
|Lotus Domino administrator password||Type the password associated with the Lotus Domino administrator user account, and press Enter.|
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 will also be generated.
(Optional) If you plan to recreate your current set of policies on the system console in the Sametime 8.5 deployment, review existing policy settings and copy them down now.
The upgraded Sametime Administration Tool no longer displays Policies after you restart the server in the next step. The only way to find policies later is to open the stpolicy.nsf database directly.
Restart the Sametime Community Server.
Parent topic: Expanding the deployment to host meetings on a Sametime Meeting Server
Previous topic: Connecting to a Sametime Community Mux server for the expanded deployment
Next topic: Registering the upgraded Community Server cluster with the System Console
After you restart the server, the SSCUserName
settings will be removed from the console.properties
file and replaced with a new SSCEncodedAuthorization
setting; for example: