Notes from upgrading IBM Connections (part 3) – Non-root user install problems

If you need to install Connections 3.0.1 Fix Pack as a non-root user there are a couple of additional steps that are not in the IBM Connections Wiki article Installing Fixes as a non-root user.

 
Non-root Install

To do a non-root install of the Connections 3.0.1 Fix Pack you need to change the -accessRights from admin to nonAdmin in the following files:

/opt/IBM/InstallationManager/eclipse/silent-install.ini
/opt/IBM/InstallationManager/eclipse/launcher.ini

 

If you don’t make this these changes and you attempt to run the install you’ll see an error like this:

Administrator privileges are required.
00:00.49 ERROR [main] com.ibm.cic.agent.internal.application.HeadlessApplication run
Administrator privileges are required.

 

How to install the Connections 3.0.1 Fix Pack as a non-root user if the initial install had been done as root

If the initial install was done as root and then ownership changed to a non-root user, as well as making sure that the <app_server_root> , the <lotus_connections_root> and the <data_directory_root> directories are owned by the non-root user you need to change ownership of the Installation manager directories, e.g.

/opt/IBM/InstallationManager/
/opt/IBM/SSPShared/
/var/ibm/InstallationManager

You also need to copy the Installation Manager registry file from :

/etc/.ibm/registry/InstallationManager.dat to
/home/<non-root user>/etc/.ibm/registry/InstallationManager.dat

 

If you don’t make these changes and you attempt to run the install you’ll see an error like this:

The Installation Manager cannot be started.The registry information does not exist or does not match with this executable.This may happen if you are trying to run Installation Manager installed by another user.
00:00.85 ERROR [main] com.ibm.cic.agent.internal.application.HeadlessApplication run
The Installation Manager cannot be started.The registry information does not exist or does not match with this executable.This may happen if you are trying to run Installation Manager installed by another user.

LC3 silent installation requires the passwords to be encrypted

During the installation of Lotus Connections 3.0, which was being performed silently with a response file, we kept getting an error on the Mobile application install phase.

The error we were getting was:
The token attribute must not be an empty string. /opt/IBM/LotusConnections/replaceAnt_removePassword.xml:388: The token attribute must not be an empty string.

This error was a little confusing as it implied that the password was missing but the response file did have a password specified for Mobile (it was the same for each of the other Lotus Connections applications) thankfully after some serious head scratching it was found that the issue was caused by the fact we had not encrypted the passwords in the response file.

I should have read the instructions more carefully as it clearly tells you to do this in the Lotus Connections wiki (Installing in silent mode).

Graphical libraries needed for silent LC3 installation?

There seems to be an issue with the silent install process for Lotus Connections 3.0 on Linux as it requires two graphical libraries (listed below) to be installed for it to work.

gtk2-2.10.4-21.el5_5.6
libgtk-java-2.8.7-3.el5

I could understand the need for these if I was running a GUI install but not when I’m running a silent install with a response file. Thankfully identifying which precise libraries were required was quick and painless (for me) due to the skill of my colleague Richard Clark (Linux Guru extraordinaire).

TDI fixpack installation error

As part of Lotus Connections 3.0 install I got this error whilst installing Fix Pack 5 for TDI on 64-bit Linux:

CTGDKO010W While executing an operating system command, a non-zero return code was returned. Return code=13; Message

The installation seemed to complete successfully but I was concerned it case it hadn’t. I removed the Fix Pack, turned on debugging (edit /opt/IBM/TDI/V7.0/etc/updateinstaller-log4j.properties and change the log level from INFO to DEBUG), and then installed the fix pack again. The install still generated the same error but the additional information being written to /opt/IBM/TDI/V7.0/logs/updateInstaller.log showed the fix pack being installed correctly.

The next step was opening a PMR with IBM; they analysed the updateInstaller.log file and confirmed the error could be ignored and that the way to confirm that the installation was successful was by running the following command:

/opt/IBM/TDI/V7.0/bin/applyUpdates.sh -queryreg

The output from the command is below and shows Fix Pack 5 has been installed:

Information from .registry file in: /opt/IBM/TDI/V7.0
Edition: Identity
Level: 7.0.0.5
License: None

Fixes Applied
=-=-=-=-=-=-=
TDI-7.0-FP0005(7.0.0.0)

Components Installed
=-=-=-=-=-=-=-=-=-=
BASE
SERVER
-TDI-7.0-FP0005
CE
-TDI-7.0-FP0005
JAVADOCS
EXAMPLES
-TDI-7.0-FP0005
EMBEDDED WEB PLATFORM
AMC
Deferred: false

Lotus Connections 3.0 – Additional download information for Linux

The IBM page “Download Lotus Connections 3.0″ which has the part numbers required for installing Lotus Connections 3.0 on Linux lists the 64-bit WebSphere Application Server components with the 32-bit WebSphere Application Server part numbers.

The correct part numbers for WebSphere Application Server 64-bit are:

  • C1G35ML WebSphere Application Server Network Deployment V7.0 for Linux on x86, 64-bit
  • C1G36ML WebSphere Application Server Network Deployment V7.0 Supplements for Linux on x86 64-bit (1 of 2)
  • C1G37ML WebSphere Application Server Network Deployment V7.0 Supplements for Linux on x86 64-bit (2 of 2)

You also need to remember to download the required Fix Packs and iFixes.

WebSphere Application Server:

TDI:

DB2 9.7:

Follow

Get every new post delivered to your Inbox.