Unregistering a clustered Community ServerAdded by IBM on November 23, 2011 | Version 1 (Original)
|To remove an IBM® Sametime Community Server from the list of the Sametime System Console's managed servers, run the unregister utility on the server. This step is required before uninstalling a Community Server that you installed without a deployment plan and then registered with the Sametime® System Console later using the registration utility. If you installed the server with a deployment plan, unregistering is only needed if you are performing some other activity that requires removal of the product from the console.
To remove an IBM
® Sametime Community Server from the list of the Sametime System Console's managed servers, run the unregister utility on the server. This step is required before uninstalling a Community Server that you installed without a deployment plan and then registered with the Sametime
® System Console later using the registration utility. If you installed the server with a deployment plan, unregistering is only needed if you are performing some other activity that requires removal of the product from the console.
Before you begin
The Sametime System Console must be started.
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:
- 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."|
Start the Sametime Community Server.
Now unregister the server:
Only the required values in this file are listed here:
Table 2. productConfig.properties settings
|DepName||The Dep Name must be the name that was used when you installed: the unique name for this deployment as known by the Sametime System Console.|
|NodeHostName ||Provide the fully qualified host name for the Community Server that is being unregistered.|
- Run the unregister utility with the following command:
As the unregister utility runs, you will be prompted enter the Location of the notes.ini file. You are only prompted for the notes.ini file location when unregistering the server. Type the full path to the directory containing the notes.ini file (for example, /stserver/data), and press Enter.
- AIX, Linux, Solaris: unregisterProductNode.sh
- Windows: unregisterProductNode.bat
The utility unregisters the server, generating a log file called ConsoleUtility.log and storing it in the console/logs directory. If the unregistration is successful, the console.pid will be removed.
Parent topic: Removing a cluster of Sametime Community servers on AIX, Linux, Solaris, or Windows
Previous topic: Removing a Sametime Community Server from a cluster
Next topic: Uninstalling a clustered Sametime Community Server
Updating the Sametime System Console on AIX, Linux, Solaris, or Windows when server unregistration fails
Command reference for starting and stopping servers