WebSphere Message Broker v8 now supports Ubuntu for development systems (i.e. not production use) - http://www-01.ibm.com/support/docview.wss?uid=swg27023600#Ubuntu
I have been running MQ and Message Broker on Ubuntu and Debian since shortly after I joined IBM in 2005, and it seems there are lots of other people doing this too despite it not being a supported platform before now.
Lots of people have advice on how to install MQ and WMB, and it is worth mentioning them in case you have problems.
The best advice I can give for installing MQ and WMB on Ubuntu is:
- change the /bin/sh symlink to point to /bin/bash – MQ Doesn’t like installing with dash as the default shell.
- use rpm to install MQ – Alien is a bit of a hack, and does not work well. You will need to use the “–force-debian” flag on rpm to make it install.
- One other thing which might help is to run the mqlicense.sh script with the ‘-console’ flag as it may not find your X applications properly.
Some user’s have noticed that chown on Debian and Ubuntu strips the setuid bit from the binaries (Debian and Ubuntu consider leaving setuid set on an executable when you change it’s owner a security flaw, whereas Redhat and SuSE appear not to) so you may need to fix the permissions (best to check the permissions of the same level of MQ from a RHEL or SLES box and set them the same) though I have not seen this with recent versions of MQ.
Message Broker v8 installs quite happily on Ubuntu. The only issues that I know of are that some of the eclipse based gui applications do not draw everything correctly. This is a known eclipse-GTK bug, and is more common on releases after Lucid Lynx (10.04). A workaround is to set the environment variable GDK_NATIVE_WINDOWS=1
Update 05/01/12 – I have just noticed that the script ‘mqsicreateworkpath’ which is used to initialise /var/mqsi correctly still uses ksh. Either install ksh on your system or edit the script to say bash in the first line instead of ksh (it should work fine then)