When you installed an IBM® Sametime® server using IBM Installation Manager, the Sametime System Console's WebSphere® administrator credentials
were stored in Installation Manager for future use during server upgrades.
If you later changed the password on the System Console, you must
update the password stored in each Sametime server's
copy of Installation Manager before attempting to upgrade. This task
also applies to clusters: if a node's WebSphere administrator credentials do
not match those stored on the cluster's deployment manager, you must
update the node's copy of Installation Manager to match the
deployment manager before attempting an upgrade.
Before you begin
Back up installRegistry.xml and installed.xml,
the two Installation Manager files you are going to modify. The default
installation path for the files is shown in the following examples.
AIX® and Linux™
var/ibm/Installation
Manager/installRegistry.xml
var/ibm/Installation
Manager/installed.xml
Windows™
drive:\Program
Data\IBM\Installation Manager\installRegistry.xml
drive:\Program
Data\IBM\Installation Manager\installed.xml
About this task
When you installed the IBM Sametime System Console,
you created an IBM WebSphere Application Server administrator
user name and password. Then, when you created deployment plans for
installing additional Sametime servers,
the copy of Installation Manager hosted on the target server retained
a copy of the System Console's credentials for later use (for
example, in upgrades). Many companies require users to change passwords
on a regular basis, so it is likely that when you are ready to upgrade,
the System Console password stored in the server's copy of Installation
Manager is no longer valid and the upgrade will fail. If the System
Console's password has changed since you installed the previous
version, you must update the appropriate copy of Installation Manager
before attempting to upgrade.
A similar issue affects clusters
that use a dedicated deployment manager instead of using the Sametime System Console
as the deployment manager. If you installed a node into a Sametime cluster using different WebSphere administrator credentials
from the cluster's deployment manager, you must update Installation
Manager on the node to match the credentials used on the deployment
manager. Even if the node's credentials have not changed, the
fact that they do not match the deployment manager's credentials
will cause an error during the upgrade.
This task is only necessary for WebSphere-based
Sametime servers that were installed using Installation Manager. Make this change on the following servers
running on AIX, Linux,
or Windows:
- Sametime System Console
- Sametime Advanced Server
- Sametime Meeting Server
- Sametime Proxy Server
- Sametime Media Manager components: Conference Manager,
SIP Proxy/Registrar, and Video Manager
Follow these steps to update the WebSphere administrator credentials stored
in Installation Manager.
Procedure
- Encrypt the password (either the new System Console password,
or the deployment manager's password).
Encrypting
the password provides a secure way to store it in the Installation
Manager files.
Attention: On some operating systems,
Sametime encounters problems
when the WebSphere administrator
password contains the ! or @ character, even though these characters
are considered valid by WebSphere Application
Server. If the password contains either of these characters, you should
change the WebSphere administrator password now
on the System Console or deployment manager before encrypting the
password and copying it into Installation Manager.
- On the computer you want to upgrade, download the generateEncodedPassword.bat or generateEncodedPassword.sh utility
provided with the Sametime installation
files (look in the generateEncodedPassword directory
under the install media's root).
-
(Windows only) Verify that the generateEncodedPassword.bat file references
the correct path for IBM Installation Manager; correct the file if necessary.
The generateEncodedPassword.bat file is coded to look for IBM Installation
Manager in the following location:
C:\Program Files\IBM\Installation Manager\eclipse\tools\imcl.exe
If this is not the correct location for your server, modify the following statement in the file
to provide the correct path before saving and closing the
file:
SET ENCODED_PASSWORD_DIR=%~dp0%
set TOOL=UNDEFINED
if EXIST "C:\IBM\Installation Manager\eclipse\tools\imcl.exe" set TOOL="C:\IBM\Installation Manager\eclipse\tools\imcl.exe"
- Run the utility from a command line with the following
syntax:
AIX and Linux
./generateEncodedPassword.sh password
Microsoft™ Windows
generateEncodedPassword.bat password
where password is
the Sametime System
Console's or the deployment manager's WebSphere administrator password.
- Copy the encrypted password into a text file for use
in the next step.
- In a text editor, update the Installation_manager_root/InstallRegistry.xml file.
- Find the Sametime Server
profile section:
<profile id='IBM Sametime
Server Platform' kind='product'>
- To change the administrator user name, update the adminid property
with the new value.
<property name='user.was.adminid'
value='admin_name'/>
- To change the password, update the password property
with the encrypted password created by the generateEncodedPassword utility.
<property name='user.was.password' value='encrypted_password'/>
- Close and save the file.
- In a text editor, update the Installation_manager_root/installed.xml file.
- Find the Sametime Server
profile section:
<location id='IBM Sametime Server Platform' kind='product'>
- To change the administrator user name, update the SSCusername property
with the new value.
<property name='user.SSCusername' value='admin_name'/>
- To change the password, update the SSCpassword property
with the encrypted password created by the generateEncodedPassword utility.
<property name='user.SSCpassword' value='encrypted_password'/>
- Close and save the file.