For some strange reason IBM does not supply the 6.2.2 ITM Linux agent as RPM package(s).
Instead a tremendous number of files with a size of 2.7G is supplied!
If SE-Linux in enabled IBM suggests to disable SE-Linux! But hang on there is help in the darkness

Make sure following packages is installed.

libstdc++-devel-4.4.5-6.el6.i686
compat-libstdc++-296-2.96-144.el6.i686
compat-libstdc++-33-3.2.3-69.el6.x86_64
compat-libstdc++-33-3.2.3-69.el6.i686
libXpm-devel-3.5.8-2.el6.x86_64

If these packages is missing you will get following error message:

runGSkit failure: Return error code: 99.
runGSkit failure: GSKit check failure, script: /opt/IBM/ITM/li6243/gs/bin/private_verifyinstall.
runGSkit failure: li6243 - GSK check error, verifyInstall test failed.
install.sh failure: Return error code: 4.

Install agent (or rather do first round of installation as SE-Linux is turned on)
Dive into directory with ITM files.
Run install script

# ./install.sh

Choose default install values.
When prompted for Select one of the following:
Select 1) Install products to the local host.

You will be met with the IBM warning sign (rubbish):
WARNING: SELinux (Secure Enhanced Linux) is set to “enforced” or “permissive” mode. “Enforced” mode is not supported by IBM Tivoli Monitoring
1. Set SELinux “disabled” mode.
2. Reboot the system.
3. Execute the “prelink -a” command before restarting the ITM installation.

The install script will fail at some time with the messages:

JVMJ9VM011W Unable to load j9jit23: /opt/IBM/ITM/JRE/lx8266/bin/libj9jit23.so: cannot restore segment prot after reloc: Permission denied
JVMJ9VM011W Unable to load jclscar_23: /opt/IBM/ITM/JRE/lx8266/bin/libjclscar_23.so: cannot restore segment prot after reloc: Permission denied
Could not create the Java virtual machine.
install.sh failure: KCI1007E terminating … license declined.

Again IBM is showing their fantastic (cough) SE-Linux knowledge. According to the IBM web page (check link) one should run:

restorecon -R -v /opt/IBM/ITM/JRE/
or
semanage fcontext -a -t textrel_shlib_t "/opt/IBM/ITM/JRE/lx8266/bin/libj9jit23.so"
semanage fcontext -a -t textrel_shlib_t "/opt/IBM/ITM/JRE/lx8266/bin/libjclscar_23.so"
chcon -R -t textrel_shlib_t /opt/IBM/ITM/JRE/lx8266/bin/libj9jit23.so
chcon -R -t textrel_shlib_t /opt/IBM/ITM/JRE/lx8266/bin/libjclscar_23.so 

Above IBM instructions is NOT correct.

restorecon should be ran after semanage & chcon will not survive relabelling of file systems……

Correct method that will survive relabelling of file systems:

# semanage fcontext -a -t textrel_shlib_t "/opt/IBM/ITM/JRE/lx8266/bin/libj9jit23.so"
# semanage fcontext -a -t textrel_shlib_t "/opt/IBM/ITM/JRE/lx8266/bin/libjclscar_23.so"
# restorecon -R -v /opt/IBM/ITM/JRE/

Then do second of installation:
re-run install.sh and install ITM agent.
When prompted insert encryption key.

Next step is to configure the ITM agent.

# /opt/IBM/ITM/bin/itmcmd config -A lz

Select default options.
When prompted for TEMS Host Name insert IP of primary Remote TEMS

Configure connection for a secondary TEMS? [1=YES, 2=NO] (Default is: 2)
Select 1 and insert IP of secondary Remote TEMS

Edit /opt/IBM/ITM/config/lz.ini and add in bottom of file:

CTIRA_HOSTNAME=<customer abbreviation>.$RUNNINGHOSTNAME$
CTIRA_SYSTEM_NAME=<customer abbreviation>.$RUNNINGHOSTNAME$
CTIRA_HEARTBEAT=3

Check configured stuff:

# /opt/IBM/ITM/bin/itmcmd config -A -g lz

Only start Linux agent (lz):

# /opt/IBM/ITM/bin/itmcmd agent start lz

Alternatively start all ITM agents:

# /etc/init.d/ITMAgents1 start

Check node is going online. Use IBM TEPS

http://www-01.ibm.com/support/docview.wss?rs=650&context=SSTFXA&uid=swg21412827&loc=en_US&cs=utf-8&lang=en

You can temporarily disable the Agent Management Services Watchdog by using the InstallDir/bin/itmcmd execute lz disarmWatchdog.sh command. This disables the Watchdog process for the OS Monitoring Agent and all Agent Management Services managed agents. If there is local administrative work to be performed, and you do not want the auto-restart of the agents to interfere with it, run the InstallDir/bin/itmcmd execute lz disarmWatchdog.sh command before proceeding. When the work is complete, recycle the OS Monitoring Agent to reenable Agent Management Services, or use the InstallDir/bin/itmcmd execute lz rearmWatchdog.sh command.

Edit the < lz | ux >.ini and comment out the line the starts with KCA_CAP_DIR. (Note the value on the right might have a slightly different value based on the release).

  # KCA_CAP_DIR=$CANDLEHOME$/config/CAP:/opt/IBM/CAP
  and add the line
  KCA_CAP_DIR=

Stop and restart the OS Agent

References:

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=%2Fcom.ibm.itm.doc_6.2.2%2Fmain_linux13.htm

https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Monitoring/page/Watchdog%20%28OS%20Agent%29