I installed IBM Rational Quality Manager 2.0.0.1 on the same machine as I installed Rational Requirements Composer before. Some steps from installation tips may be needed.
The official product documentation does not give the exact DB2 command line command. If you use the command from RTC manual, the table creation will fail. This is caused by the pagesize being too small. Use this command to create the database instead:
db2 create database RQM using codeset UTF-8 territory en PAGESIZE 16384
Another post, where the main audience is me :)
To install IBM Rational Requirements Composer 2.0.0.1 on 64bit Linux, you need 32bit libraries installed. Strange error message is displayed otherwise when trying to run the installer:
root@rtc:/opt/rrc-install/RRCS_SETUP/InstallerImage_linux# ./install bash: ./install: No such file or directory
To install the needed libraries run:
apt-get install ia32-libs
The installation should run successfully after this.
RRC needs swt-gtk to run. Install it by:
apt-get install libswt-gtk-3.4-jni
In addition, RRC needs a X screen to start. There is an IBM Technote with solution for RHEL and Suse. To install Xvfb on Ubuntu do:
apt-get install xvfb
The rest of the procedure (starting the server) is the same as on RHEL or SLES (see the technote).
The server is started by server.startup. This script has to be called from its directory – you need to cd first. The init script can look for example like this:
#!/bin/bash
#
# rrc Startup script for the RRC
#
# chkconfig: - 90 16
# description: Rational Requirements composer \
# processname: java
# pidfile: /var/run/rrc.pid
#
prog=rrc
pidfile=${PIDFILE-/var/run/rrc.pid}
lockfile=${LOCKFILE-/var/lock/rrc}
rrchome=/opt/rrc/server
RETVAL=0
start() {
echo -n $"Starting $prog: "
# export GTK_PATH=/usr/lib32/gtk-2.0
Xvfb :1 -screen 0 800x600x24&
cd ${rrchome}
DISPLAY=localhost:1.0 ./server.startup
RETVAL=$?
echo
[ $RETVAL = 0 ] && touch ${lockfile}
return $RETVAL
}
stop() {
echo -n $"Stopping $prog: "
${rrchome}/server.shutdown
RETVAL=$?
killall Xvfb
echo
[ $RETVAL = 0 ] && rm -f ${lockfile} ${pidfile}
}
# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
status)
status $prog
RETVAL=$?
;;
restart)
stop
start
;;
*)
echo $"Usage: $prog {start|stop|restart}"
RETVAL=3
esac
exit $RETVAL
OS details: Ubuntu 9.04, Server edition, 64bit
I'm currently installing Jazz CALM solution on CentOS 4 64bit (equivalent to RHEL 4 64bit). I got stuck when installing both Rational Quality Manager (RQM) and Rational Requirements Composer (RRC). Both need to be installed via IBM Installation Manager. RRC installation package includes IBM Installation Manager, whereas RQM doesn't.
To install IBM Installation manager on 64bit RHEL 4 you first need to install these:
yum install gtk2.i386 libgcc.i386I first installed libgcc.i386 only to get rid of the error message
libgcc_s.so.1 must be installed for pthread_cancel to work
After this, there was no error message, but the installer returned exit code 13 (which I haven't found documented anywhere). Installing 32bit gtk library solved the problem.
The IBM Installation Manager itself can be downloaded from ftp://public.dhe.ibm.com/…alsdp/v7/im/
I hope this helps somebody save some time of desperate googling for solution…
Installation of Rational Team Concert is in general as easy as unzipping the downloaded archive. I did this recently on Ubuntu 9.04 64bit, server edition. Later I have encountered errors when generating any report (for example Floating License Report). I got this message:
CREATE_EXTENSION_FAIL ( 1 time(s) )
detail : org.eclipse.birt.report.engine.api.EngineException: CREATE_EXTENSION_FAIL
at org.eclipse.birt.report.engine.executor.ExecutionContext.addException(ExecutionContext.java:1121)
....The post at
jazz.net forums suggested, that there are missing libraries required by file
*/jazz/server/jre/bin/libfontmanager.so You can find out which
libraries are missing by running
ldd jazz/server/jre/bin/libfontmanager.so
My output was:
linux-vdso.so.1 => (0x00007fff5efad000)
libdl.so.2 => /lib/libdl.so.2 (0x00007fc04eed9000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007fc04ecbd000)
libwrappers.so => not found
libawt.so => not found
libstdc++.so.5 => not found
libm.so.6 => /lib/libm.so.6 (0x00007fc04ea36000)
libX11.so.6 => /usr/lib/libX11.so.6 (0x00007fc04e72f000)
libc.so.6 => /lib/libc.so.6 (0x00007fc04e3bd000)
/lib64/ld-linux-x86-64.so.2 (0x00007fc04f26f000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007fc04e1a0000)
libXau.so.6 => /usr/lib/libXau.so.6 (0x00007fc04df9d000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007fc04dd98000)The system library that was missing in my system (using default installation of Ubuntu 9.04 64bit, Server edition) was libstdc++.so.5. This library is included in the package libstdc++5. It can be installed by running:
apt-get install libstdc++5
The RTC server has to be restarted afterwards.
jazz/server/server.shutdown jazz/server/server.startup
While fighting with DB2 denying logins I had to change the default hash algorithm used to store passwords in /etc/shadow.
As far as I know (and as grep -i -r "sha512" /etc/* tells me
), there are two files that carry this information.
Namely /etc/pam.d/common-password and
/etc/login.defs.
To change the algorithm from sha512 (which shifts as the default in the new Ubuntu releases) change this:
password [success=1 default=ignore] pam_unix.so obscure sha512
to
password [success=1 default=ignore] pam_unix.so obscure md5
ENCRYPT_METHOD SHA512
to
ENCRYPT_METHOD MD5
This howto is mostly built on the great tutorial available at http://www.comnetslash.com/…hout-reboot/. My spot tries to be more Ubuntu and LVM specific. This manual was tested on Ubuntu 9.04 (jaunty) Server edition guest OS.
A new hard disk can be added
easily to a running virtual machine in VMWare Infrastructure Web Access by
clicking Add Hardware and following the wizard.
Note: I assume that all of the commands given are run under superuser (root) rights. To become root type
sudo su rootThe package scsitools provides the script rescan-scsi-bus.sh, which does exacly what we need. Install it and run it:
apt-get install scsitools
rescan-scsi-bus.shThis should detect the newly added hard disk and make it available in
/dev/ – /dev/sdb in the case you are adding a new
drive for the first time. The output of fdisk -l should include the
newly detected disk.
Format the newly detected drive using fdisk
fdisk /dev/sdb
n (for new partition)
p (for primary partition)
1 (partition number)
(keep the other values default)
w (write changes)Change the type of the partition to LVM Linux:
fdisk /dev/sdb
t (change the partition type)
8e (for Linux LVM)
w (write changes)pvcreate /dev/sdb1List the Volume groups available at your machine.
vgdisplayReplace VolGroupName with what you read from the output of the last command.
vgextend VolGroupName /dev/sdb1You should see the newly aquired free space in the output of
vgdisplayAfter adding some free space to your Volume Group, you can distribute it to the Logical Volumes. The list of Logical Volumes can be obtained by running
lvdisplayRun the following commands for each Logical Volume you want to resize (add space to). Again – replace /dev/VolGroupName/Name with the Logical Volume name you can read from the output of the last command. The +10G means Add 10 GB
lvextend -L +10G /dev/VolGroupName/NameThe last step is to resize the ext3 filesystem (use different tool is you use different filesystem):
resize2fs /dev/VolGroupName/NameI switched one server from Fedora Core to Ubuntu yesterday. Shibboleth 2 SP installation is a bit more tricky under Ubuntu than Fedora Core. The packages are not available in the Ubuntu repositories, but Satya's blog serves a working howto.
Shibboleth seemed to be working well after installation, but today it was down dumping
2009–06–23 12:51:53 ERROR Shibboleth.Listener : socket call resulted in error (2): no message 2009–06–23 12:51:53 CRIT Shibboleth.Listener : failed to bind to socket.
into the /var/log/shibboleth/shibd.log. I luckily found a
solution in quite a short time. The problem was that the shibd was trying to
create socket in /var/run/shibboleth directory, which did not
exist. Creating it once does not help because Ubuntu removes content of
/var/run/ at every reboot. To fix it this has to be added
to /etc/init.d/shibd
if [ ! -e /var/run/shibboleth ] then mkdir /var/run/shibboleth fi
If you are getting
SQL30082N Security processing failed with reason „15“ („PROCESSING FAILURE“)
when connecting to the db2 database using db2 CONNECT TO dbname USER
username or
Connection authorization failure occurred. Reason: Local security service non-retryable error. ERRORCODE=-4214, SQLSTATE=28000
when connecting remotely (via JDBC driver) read on. I finally found what causes this error and a solution!
[ad]
Tho whole problem is in the format of the passwords in
/etc/shadow. DB2 doesn't seem to like the passwords generated when
changing password using the standard passwd command. In Fedora Core
10 the password is hashed using sha-512 and the entry for user
username looks like:
username:$6$efWWOYRY$z5DNL1kLQU4AmPkFBqbQh6LOh0Qjxq654dS9jE46iPNp8Zces8I4bP8GLZ3G3RWLo/6o.LYOV5neYSKxXbL.M1:14375:0:99999:7:::
DB2 works fine with passwords hashed with standard crypt function. Password
in the desired format can be obtained by calling openssl passwd
desiredPassword. The output of openssl can be passed to usermod
--password The complete command to change user's password then
look like:
usermod --password `openssl passwd desiredPassword` usename
I tried to hand-edit /etc/shadow and insert salted MD5 password, which can
be obtained by openssl passwd -1 desiredPassword and the connection
was sucessfuly established. To sum it up, the whole problem in the end seems to
be that DB2 doesn't like SHA-512 hashes in /etc/shadow. On the other hand, it
works fine with hashes generated by crypt and MD5.
Fedora Core contains a nice tool authconfig. To change the
default hashing algorithm to MD5 run
authconfig –passalgo md5 –update
All the passwords inserted in the password database will be stored in MD5 from now on. It will, of course, not change the hashes of the current passwords.
Ubuntu ships with sha512 as default hash algorithm for passwords in
/etc/shadow. The easiest way to change the default algorithm is to
edit the file /etc/pam.d/common-password and change the line that reads
password [success=1 default=ignore] pam_unix.so obscure sha512
to
password [success=1 default=ignore] pam_unix.so obscure md5
The information about the algorith is also included in the file
/etc/login.defs, which is used by chpasswd for
example. Therefore change the line
ENCRYPT_METHOD SHA512
to
ENCRYPT_METHOD MD5
I got 2 errors while installing DB2 Express that comes with Rational Team Concert. Two libraries were missing:
ERROR: The required library file libstdc++.so.5 is not found on the system.
Solution: (thanks http://tldp.org/…fedora6.html)
yum -y install compat-libstdc++-33
ERROR: The required library file libaio++.so.1 is not found on the system.
Solution:
yum -y install libaio
Today I ran apt-get update && apt-get dist-upgrade on
my Debian Lenny installed on WD MyBook as I ussually do. It removed VIM (I let
it as I thought it was just replaced by another package). I tried to run
vim after the upgrade but it was really uninstalled. Trying to
install it again by apt-get install I got
The following packages have unmet dependencies:
vim: Depends: vim-runtime (= 1:7.1.293-3)
but 1:7.1.293-3+lenny1 is to be installed
E: Broken packagesI tried to uninstall vim-runtime. It didn't help. I don't have time to solve it now so I can't give a solution. If you encountered the same problem and have a solution to this problem, I'd really appretiate your comment.
It's quite sad that Debian repository is not consistent and one gets errors
using apt-get.