Update: This post is now super-seeded by the last version, installing FileNet P8. I will still be answering any question you might have though.

IBM came up with something that sounds really nice: The Composite Platform Installation Tools or also called CPIT. And it is true, being able to have a running platform (for test and development only) in less than one hour sounds like a dream, especially when you know how installing P8 is a nightmare. Except it never works…

And from the one hour expected, we fall back to a few days like before. It is actually impressive how many errors this thing can produce. That’s why I write this post, trying to summarize all errors that can occur.

How to start CPIT

To start a CPIT installation, you need to have the following components renamed as follow:

• IBM Content Platform Engine 5.2: ce.tar.gz
• IBM Content Platform Engine Client 5.2: cec.tar.gz
• IBM Tivoli Directory Server 6.3 Client-Server: tds.tar
• GSKit for Tivoli Directory Server 6.3: tdsgskit.tar
• IBM DB2 9.7 Restricted License: db2lic.zip
• IBM WebSphere Application Server 8.5: WAS_V8.5_1_OF_3.zip, WAS_V8.5_2_OF_3.zip, WAS_V8.5_3_OF_3.zip
• IBM Installation Manager 1.5.2: im.zip
• IBM Content Navigator 2.0.2: icn.tar (if you wish to install ICN 2.0.3 IF001 during CPIT, see my other post on how to modify the CPIT script)
• IBM DB2 9.7 Fix Pack 5: db2.tar.gz

I strongly recommend you to use the Case foundation CPIT (CIKW2EN) and not the P8 CPIT because there is some (more) issues with it. You won’t have Workplace XT installed with the Case Foundation CPIT but at least it will work, and installing Workplace XT is actually quite easy.

First think to do is check all your archives, because they may easily get corrupted because of their size. Either decompress them or use a tool to test them (7-zip for instance).

Then decompress the CPIT tool and modify the cpit.properties to accept all licences:

LICENSE_ACCEPTED_#=FALSE # becomes
LICENSE_ACCEPTED_#=TRUE

Then just launch the installer (adapt to your version):

./5.2.0.0-ICF-CPIT-LINUX.BIN

What to do after the CPIT

After you finished running the CPIT, don’t forget the last few steps to have you platform fully working and stable. Also the platform is not configured to start by itself after a reboot, you can find here scripts to start and stop the platform, you can add them to the services if you want.

Finally you would have to create an object store, because there is only one created by the CPIT installer and it is intended for configuration purpose, so you would want one to store content. Here is the How To for this.

Script to avoid as much errors as we can

Here is a script I usually run before running a CPIT installation, this is all fixes from the Errors list section. You can either use this, or just fix error one by one if you wish to understand better what’s going on. But be careful, if you fix errors on the go, you will have to rollback your VM to before starting the CPIT installation, because some of them are not recoverable. So make sure to make a snapshot just before starting, and definitely use the script if you are not on a VM. And I will recommend you to take a live snapshot (including RAM), so you can be ready to start again in seconds or it will drive you crazy 🙂

#!/bin/sh
# Set your hostname here
export NAME=
# Set your cpit folder here (the one containing the bin file)
export cpit_folder=
# Password you will be using for the CPIT installation
export PASSWORD=

echo ===============================================================
echo = Setting up hostname...
echo ===============================================================
sed -i "s/HOSTNAME=.*$/HOSTNAME=$NAME/g" /etc/sysconfig/network
hostname $NAME
sed -i "s/localhost4\slocalhost4.localdomain4\s*$/localhost4 localhost4.localdomain4 $NAME/g" /etc/hosts
sed -i "s/localhost6\slocalhost6.localdomain6\s*$/localhost6 localhost6.localdomain6 $NAME/g" /etc/hosts
echo $NAME > /etc/HOSTNAME
echo ===============================================================
echo = Hostname set up
echo ===============================================================
echo ===============================================================
echo = Installing pre-requisites...
echo ===============================================================
# For the installer
yum install -y ld-linux.so.2
yum install -y libgcc_s.so.1
# X and co for the installer
yum install -y libX11.so.6 libXp.i686 libXp.x86_64 libXpm.i686 libXpm.x86_64 gtk2.x86_64 gtk2.i686 libXft.i686 libXft.x86_64 libXmu.i686 libXmu.x86_64 libXtst.i686 libXtst.x86_64
# gcc and co
yum install -y libgcc_s.so.1 libaio.x86_64 libstdc++.so.5 libstdc++.so.6 bc unzip glibc.i686 libgcc.i686 libgcc.x86_64 libstdc++.so.5 compat-libstdc++-33.i686 compat-libstdc++-33.x86_64
# ksh for TDS
yum install -y ksh ksh.x86_64
# Pre-requisites I did not have issues with but we never know
yum install -y compat-db47.i686 compat-db47.x86_64
yum install -y pam.i686 pam.x86_64
yum install -y elfutils.x86_64 elfutils-libs.i686 elfutils-libs.x86_64
yum install -y rpm-build.x86_64
# some utilities
yum install -y unzip gunzip sed

/usr/sbin/setenforce 0
echo ===============================================================
echo = Pre-requisites installed
echo ===============================================================

echo ===============================================================
echo = Creating symbolic link...
echo ===============================================================
ln -s /bin/ksh /usr/bin/ksh
mkdir /opt/IBM
ln -s /opt/IBM /opt/ibm
echo ===============================================================
echo = Symbolic links created
echo ===============================================================

echo ===============================================================
echo = Increasing WebSphere heap size...
echo ===============================================================
echo "AdminTask.setJVMInitialHeapSize( \"[ -nodeName P8Node01 -serverName server1 -initialHeapSize 512 ]\" )" > /opt/heapsize.py
echo "AdminTask.setJVMMaxHeapSize( \"[ -nodeName P8Node01 -serverName server1 -maximumHeapSize 2048 ]\" )" >> /opt/heapsize.py
echo "AdminConfig.save()" >> /opt/heapsize.py
echo >> /opt/heapsize.py

sed -i "s/InstallerName server1\s*$/InstallerName server1\n\t.\/wsadmin.sh -username P8Admin -password $PASSWORD -conntype SOAP -profileName AppSrv01 -lang jython -f \"\/opt\/heapsize.py\"\n\t.\/stopServer.sh server1 -username P8Admin -password $PASSWORD\n\t.\/\$InstallerName server1\n/g" $cpit_folder/install-scripts/startWAS85.sh
echo ===============================================================
echo = WebSphere heap size increased on the startWAS85.sh script
echo ===============================================================

echo ===============================================================
echo = Writing setDB2port.sh file...
echo ===============================================================
echo '#!/bin/sh' > $cpit_folder/install-scripts/setDB2port.sh
echo "#" >> $cpit_folder/install-scripts/setDB2port.sh
echo "# Licensed Materials - Property of IBM" >> $cpit_folder/install-scripts/setDB2port.sh
echo "# 5725A15, 5724R81" >> $cpit_folder/install-scripts/setDB2port.sh
echo "# (c) Copyright IBM Corp. 2010, 2011 All Rights Reserved." >> $cpit_folder/install-scripts/setDB2port.sh
echo "# US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp." >> $cpit_folder/install-scripts/setDB2port.sh
echo "#" >> $cpit_folder/install-scripts/setDB2port.sh
echo "# parameter 1 = installerScriptFolder - Script folder" >> $cpit_folder/install-scripts/setDB2port.sh
echo "# parameter 2 = decompressedFolder - Destination folder to decompress files to" >> $cpit_folder/install-scripts/setDB2port.sh
echo "# parameter 3 = p8DownloadFolder - Source folder of the IBM software packages" >> $cpit_folder/install-scripts/setDB2port.sh
echo "# parameter 4 = 32 or 64 - Bitness of the OS 64 or 32 (optional)" >> $cpit_folder/install-scripts/setDB2port.sh
echo "#" >> $cpit_folder/install-scripts/setDB2port.sh
echo "echo \"==========================================\"" >> $cpit_folder/install-scripts/setDB2port.sh
echo "echo \"Configuring DB2 Port ..\"" >> $cpit_folder/install-scripts/setDB2port.sh
echo "date" >> $cpit_folder/install-scripts/setDB2port.sh
echo >> $cpit_folder/install-scripts/setDB2port.sh
echo "#su - dsrdbm01" >> $cpit_folder/install-scripts/setDB2port.sh
echo "db2 update dbm cfg using SVCENAME 3737" >> $cpit_folder/install-scripts/setDB2port.sh
echo "db2stop FORCE" >> $cpit_folder/install-scripts/setDB2port.sh
echo "db2start" >> $cpit_folder/install-scripts/setDB2port.sh
echo "db2 get dbm cfg | grep SVCENAME" >> $cpit_folder/install-scripts/setDB2port.sh
echo >> $cpit_folder/install-scripts/setDB2port.sh
echo "exit" >> $cpit_folder/install-scripts/setDB2port.sh
echo >> $cpit_folder/install-scripts/setDB2port.sh
echo "cd /var" >> $cpit_folder/install-scripts/setDB2port.sh
echo >> $cpit_folder/install-scripts/setDB2port.sh
echo "echo \"===========================================\"" >> $cpit_folder/install-scripts/setDB2port.sh
echo "date" >> $cpit_folder/install-scripts/setDB2port.sh
echo "echo \"Configured DB2 Port...\"" >> $cpit_folder/install-scripts/setDB2port.sh
echo "echo \"===========================================\"">> $cpit_folder/install-scripts/setDB2port.sh
echo ===============================================================
echo = setDB2port.sh file written
echo ===============================================================

Errors list

Here are all the errors I had to deal with. Of course I followed no requirements at all for this exercise, which is a dumb idea. But this way I could get a lot of error and reference them for later use. Hopefully it can help you and spare you some time figuring out where your error is coming from.

ld-linux.so.2 missing

./5.2.0.0-ICF-CPIT-LINUX.BIN: /tmp/install.dir.2856/Linux/resource/jre/jre/bin/java: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
./5.2.0.0-ICF-CPIT-LINUX.BIN: line 3319: /tmp/install.dir.2856/Linux/resource/jre/jre/bin/java: Success

ld-linux.so.2 library is missing.

yum install -y ld-linux.so.2

libgcc_s.so.1 missing

libgcc_s.so.1 must be installed for pthread_cancel to work

libgcc_s.so.1 library is missing

yum install -y libgcc_s.so.1

 Graphical installers are not supported by the VM

Graphical installers are not supported by the VM. The console mode will be used instead...

Some X libraries are missing:

yum install -y libX11.so.6 libXp.i686 libXp.x86_64 libXpm.i686 libXpm.x86_64 gtk2.x86_64 gtk2.i686 libXft.i686 libXft.x86_64 libXmu.i686 libXmu.x86_64 libXtst.i686 libXtst.x86_64

It is true it night be a bit too much for it did the trick for me.

File not found

Cmd Remove Ctrl-M: /opt/IBM/cpit/install-scripts/pitutil.sh /FileNet/CPIT/CIKW2EN - ICONF_CPIT_5.2_LINUX_EN/install-scripts/FIllData.sh /opt/IBM/cpit/install-scripts/FIllData.sh
OUTPUT>tr /FileNet/CPIT/CIKW2EN -

Do not use any space in the path of your CPIT folder, it won’t work!

/opt/IBM/ldap/V6.3/sbin/idsldif2db not found. TDS installation failed.

OUTPUT>==========================================
OUTPUT>Begin installTDS63.sh
OUTPUT>Tue Oct 28 10:54:09 CET 2014
OUTPUT>==========================================
OUTPUT>Setting Directories...
OUTPUT>Tue Oct 28 10:54:09 CET 2014
ERROR>chmod: cannot access `/opt/ibm': No such file or directory
OUTPUT>/opt/IBM/cpit/decompressed/TDS/tdsV6.3/tds
ERROR>./install_tds.bin: line 1956: warning: here-document at line 1956 delimited by end-of-file (wanted `/dev/null')
OUTPUT>ERROR: /opt/IBM/ldap/V6.3/sbin/idsldif2db not found. TDS installation failed.
Process completed with exit code: 1
ERROR in InvokeScripts-function - Terminate the remaining scripts.
***Aborting InvokeScripts-Install function.

Well this one is tricky because TDS failure can come from hundred of reasons. At this point you should also look in the log directory under the CPIT folder installation (usually /opt/IBM/CPIT/install-scripts/log), and open the intalltds63.txt file. Here are some commons errors.

Error getting Local Host

In initOSConstants
(Oct 28, 2014 11:10:57 AM), null, com.ibm.ldap.install.beans.LdapInit, dbg, Setting System Property LINUX to YES
Client Size is: 9000000
(Oct 28, 2014 11:10:57 AM), null, com.ibm.ldap.install.beans.LdapInit, dbg, Setting indexes for Server Install
(Oct 28, 2014 11:10:57 AM), null, com.ibm.ldap.install.beans.LdapInit, err, java.net.UnknownHostException: pit: pit
java.net.UnknownHostException: pit: pit
 at java.net.InetAddress.getLocalHost(InetAddress.java:1496)
 at com.ibm.ldap.install.beans.LdapInit.InitUser(LdapInit.java:746)
 at com.ibm.ldap.install.beans.LdapInit.execute(LdapInit.java:197)
 at com.installshield.wizard.StandardWizardListener.execute(Unknown Source)
 at com.installshield.wizard.StandardWizardListener.currentBeanChanged(Unknown Source)
 at com.installshield.wizard.Wizard$RunThread.run(Wizard.java:1822)
(Oct 28, 2014 11:10:57 AM), null, com.ibm.ldap.install.beans.LdapInit, err, error getting Local Host

Well at least with this file it’s clear, our VM doesn’t know it self :). Let’s fix properly the hostname. Since we do it for TDS you won’t have the chance to see it, but this is actually really important for many other components, including DB2, CE, Oracle if we were using oracle and so on… Anyway, ALWAYS properly set the hostname or you will have a lot of troubles.

# Replace pit with your hostname
NAME=pit
sed -i "s/HOSTNAME=.*$/HOSTNAME=$NAME/g" /etc/sysconfig/network
hostname $NAME
sed -i "s/localhost4\slocalhost4.localdomain4\s*$/localhost4 localhost4.localdomain4 $NAME/g" /etc/hosts
sed -i "s/localhost6\slocalhost6.localdomain6\s*$/localhost6 localhost6.localdomain6 $NAME/g" /etc/hosts
echo $NAME > /etc/HOSTNAME

The last is actually for websphere but since it is about hostname, let’s do it now.

java.lang.NullPointerException

Also another cause of failure for TDS installation is that it requires KSH, if you don’t have KSH it could lead to errors like this in the installtds63.txt log file:

(Oct 28, 2014 11:58:41 AM), null, com.installshield.wizardx.actions.ExecWizardAction, err, java.lang.NullPointerException
java.lang.NullPointerException
 at com.installshield.util.ProcessExec.executeProcess(Unknown Source)
 at com.installshield.wizardx.actions.ExecWizardAction.executeProcess(Unknown Source)
 at com.installshield.wizardx.actions.ExecWizardAction.run(Unknown Source)
 at java.lang.Thread.run(Thread.java:736)
(Oct 28, 2014 11:58:42 AM), null, com.installshield.wizardx.actions.ExecWizardAction, err, java.lang.NullPointerException
java.lang.NullPointerException
 at com.installshield.util.ProcessExec.executeProcess(Unknown Source)
 at com.installshield.wizardx.actions.ExecWizardAction.executeProcess(Unknown Source)
 at com.installshield.wizardx.actions.ExecWizardAction.run(Unknown Source)
 at java.lang.Thread.run(Thread.java:736)

To fix this, install KSH and also create link in /usr/bin

yum install -y ksh
ln -s /bin/ksh /usr/bin/ksh

File not found

Also depending of the CPIT version you’re using, to might encounter an issue some version of CPIT doesn’t do any difference between /opt/IBM and /opt/ibm, but as you know linux does. That why we have to help a little bit here:

mkdir /opt/IBM
ln -s /opt/IBM /opt/ibm

This should do the trick.

 ConficCE.sh task failed: Failed to connect to the DataSource

OUTPUT>==========================================
OUTPUT>Begin configCE.sh
OUTPUT>Tue Oct 28 12:36:35 CET 2014
OUTPUT>==========================================
OUTPUT>Setting Directories...
OUTPUT>Tue Oct 28 12:36:35 CET 2014
OUTPUT>Starting to run all of the tasks in profile ConfigCE.
OUTPUT>
OUTPUT>Configure Object Store JDBC Data Sources *****
OUTPUT>There was an error executing the Configure Object Store JDBC Data Sources task.
OUTPUT>Running the task failed with the following message: The data source configuration failed: 
OUTPUT>WASX7209I: Connected to process "server1" on node P8Node01 using SOAP connector; The type of process is: UnManagedProcess
OUTPUT>testing Database connection
OUTPUT>DSRA8040I: Failed to connect to the DataSource. Encountered java.sql.SQLException: [jcc][t4][2043][11550][3.63.75] Exception java.net.ConnectException: Error opening socket to server localhost/127.0.0.1 on port 3,737 with message: Connection refused. ERRORCODE=-4499, SQLSTATE=08001 DSRA0010E: SQL State = 08001, Error Code = -4,499.
OUTPUT>
OUTPUT>
OUTPUT>For additional logging information, see log file:
OUTPUT>/root/configmgr_workspace/.metadata/.log
OUTPUT>Tue Oct 28 12:36:53 CET 2014
OUTPUT>ERROR - configCE failed. Refer to /opt/IBM/cpit/install-scripts/profiles/ConfigCE/status for more details.
Process completed with exit code: 1
ERROR in InvokeScripts-function - Terminate the remaining scripts.
***Aborting InvokeScripts-Install function.

Obviously there is something wrong with the database. This one took me a little while but I actually discover that for a strange reason, IBM just omitted a file in the installation script. the file setDB2port.sh is missing. Before launching the CPIT installation, create a file setDB2port.sh in the folder install-scripts of your CPIT folder (CPIT/install-scripts/setDB2port.sh) and edit it with the following content:

#!/bin/sh
#
# Licensed Materials - Property of IBM
# 5725A15, 5724R81
# (c) Copyright IBM Corp. 2010, 2011 All Rights Reserved.
# US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
#
# parameter 1 = installerScriptFolder - Script folder
# parameter 2 = decompressedFolder - Destination folder to decompress files to
# parameter 3 = p8DownloadFolder - Source folder of the IBM software packages
# parameter 4 = 32 or 64 - Bitness of the OS 64 or 32 (optional)
#
echo "=========================================="
echo "Configuring DB2 Port .."
date 

#su - dsrdbm01
db2 update dbm cfg using SVCENAME 3737
db2stop FORCE
db2start
db2 get dbm cfg | grep SVCENAME 

exit 

cd /var 

echo "==========================================="
date
echo "Configured DB2 Port..."
echo "==========================================="

Then start again a fresh install (here is why snapshots are important 🙂 )

ConnectorNotAvailableException

Sometimes, not always, you might also have an error on the task configNexus (24/26), when deploying IBM Content Navigator. The logs in the CPIT log file are not really explicit:

OUTPUT>ADMA5011I: The cleanup of the temp directory for application navigator is complete.
OUTPUT>ADMA5013I: Application navigator installed successfully.
OUTPUT>WASX7017E: Exception received while running file "/opt/IBM/ECMClient/configure/tmp/deployapplication.tcl"; exception information: com.ibm.websphere.management.exception.ConfigServiceException
OUTPUT>com.ibm.websphere.management.exception.ConnectorNotAvailableException
OUTPUT>org.apache.soap.SOAPException: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error parsing HTTP status line "": java.util.NoSuchElementException; targetException=java.lang.IllegalArgumentException: Error parsing HTTP status line "": java.util.NoSuchElementException]
OUTPUT>
OUTPUT> -Xmca32K RAM class segment increment
OUTPUT> -Xmco128K ROM class segment increment
OUTPUT> -Xmns128M initial new space size
OUTPUT> -Xmnx256M maximum new space size
OUTPUT> -Xms512M initial memory size
OUTPUT> -Xmos384M initial old space size
OUTPUT> -Xmox1G maximum old space size
OUTPUT> -Xmx1G memory maximum
OUTPUT> -Xmr16K remembered set size
OUTPUT> -Xmso256K operating system thread stack size
OUTPUT> -Xiss2K java thread stack initial size
OUTPUT> -Xssi16K java thread stack increment
OUTPUT> -Xss512K java thread stack maximum size
OUTPUT>
OUTPUT>
OUTPUT>For additional logging information, see log file:
OUTPUT>/root/nexus_configmgr_workspace/.metadata/.log
OUTPUT>Tue Oct 28 14:36:53 CET 2014
OUTPUT>ERROR - configNexus failed. Refer to /opt/IBM/cpit/install-scripts/profiles/NexusConfig/status for more details.
Process completed with exit code: 1
ERROR in InvokeScripts-function - Terminate the remaining scripts.
***Aborting InvokeScripts-Install function.

It is best to look into the Websphere’s server logs, which are usually more explicit. If you forget they are in /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1 :). In my case I had

[10/28/14 18:09:11:518 CET] 000000a5 FileRepositor A ADMR0016I: User localhost:389/P8Admin modified document cells/P8Node01Cell/nodes/P8Node01/serverindex.xml.
[10/28/14 18:09:10:946 CET] 000000bd Ffdc I com.ibm.ffdc.impl.Ffdc setFailsafeProvider FFDC1001I: FFDC provider aborted with exception {0}
 java.lang.OutOfMemoryError: Java heap space
 at com.ibm.ffdc.util.provider.FfdcProvider.getFfdc(FfdcProvider.java:281)
 at com.ibm.ffdc.util.provider.FfdcProvider.log(FfdcProvider.java:290)
 at com.ibm.ffdc.impl.Ffdc.log(Ffdc.java:225)
 at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:136)
 at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1783)

Which is better. To fix this you have two solution, make sure you set the /etc/HOSTNAME file and the symbolic link so we have only one /opt/ibm folder (no idea why it helps but it does) and try again:

echo $NAME > /etc/HOSTNAME
mkdir /opt/IBM
ln -s /opt/IBM /opt/ibm

Or if you still get the error again and again, you can hack the CPIT installer to update the heap size, for this create a file heapsize.tcl, for example in /opt and edit it with the following content:

AdminTask.setJVMInitialHeapSize( "[ -nodeName P8Node01 -serverName server1 -initialHeapSize 512 ]" )
AdminTask.setJVMMaxHeapSize( "[ -nodeName P8Node01 -serverName server1 -maximumHeapSize 2048 ]" )
AdminConfig.save()

And edit the script install-script/startWAS85.sh to add the line the following line after the start commandafter, like this (don’t forget to replace YourPassword):

if [ -e $InstallerName ] ;then
 ./$InstallerName server1
 /opt/ibm/WebSphere/AppServer/profiles/AppSrv01/bin/wsadmin.sh -username P8Admin -password YourPassword -conntype SOAP -profileName AppSrv01 -lang jacl -f "/opt/heapsize.tcl"
 date
 echo "End startWAS85.sh"
 echo "===================="
else
 echo /opt/ibm/WebSphere/AppServer/bin/$InstallerName not found!
 exit 1
fi

Then start again 🙂