|
|
By Anton Piatek, on December 15th, 2011% Now that you know that you can use Message Broker v8 on Ubuntu for development, you may be wondering if you can use some of the databases that are more common on Linux, such as MySQL. You can!
IBM WebSphere Message Broker now uses UnixODBC to connect to many databases. Though not supported by IBM, you can actually connect to MySQL from Message Broker using UnixODBC.
Continue reading Message Broker v8 with MySQL
By Anton Piatek, on December 14th, 2011% 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.
http://www.reidmorrison.com/linux/install-websphere-mq-on-ubuntu
http://www.gefira.pl/blog/2010/07/03/websphere-mq-and-ubuntu-howto/
http://blog.herbert.groot.jebbink.nl/2009/06/wmb-61-ubuntu-904.html
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)
By Anton Piatek, on December 8th, 2011% I have been flicking through the following FAQ on the GNU GPL: Frequently Asked Questions about the GNU GPL – GNU Project – Free Software Foundation (FSF). I am trying to understand the risks that we are told about regularly in IBM of working with/on Open Source code.
I have to say that most of the risks are rather undefined, and no real examples are given. I am having trouble figuring out why IBM is so scared of its employees working with Open Source, and yet at the same time encouraging it (I run Debian on my laptop, and in fact run a Debian server distributing internal tools packaged specially for other Debian users).
The one big concern is of course patents. Personal views on software patents aside, if I were to code a patented idea into some GPL’d code and release it (as an IBM employee) then quite likely that patent will be considered GPL’d and could be used by others – the extent of patents in GPL’d code is untested in court, hence the reason for v3 of the GPL, which will probably explicitly state that any patents are given away under the terms of the GPL if in GPL’d code.
However, even if not modifying the code there is still a huge concern about working with it. Even releasing code that is dynamically linked against a LGPL’d library is incredibly hard to get approved. Why should it be? The FAQ above makes clear that if the library is LGPL’d, then dynamic linking (i.e. using a JAR file in Java) means that the library source must be available and some reverse engineering of the interaction between the two is allowed (in case someone wanted to rewrite the library). Your code does not have to be Open Sourced. Is it simply that shipping the source code is too much effort? Surely if I use a prebuilt JAR, and dump a zip of the corresponding source of a LGPL’d library in the zip I am shipping then that is it. I am complying with the terms of the GPL.
The only thing I can think of is the other side of Patents – somebody else has a patent on something in the GPL code, but the authors of the GPL code were not aware of this. If IBM were to ship GPL’d code that a competitor had a Patent on part of then indeed they would be liable for infringement, not just the author of the code. Is this risk likely? Well, SuSE have just signed a deal with Microsoft for this reason, but RedHat and Ubuntu have declined the deal. Maybe with the GPLv3 this will be less of a problem, as if another company releases GPL code then they will be explicitely releasing any patents on it too.
What if the patent holder is another third party. IBM could still be in trouble if a competitor finds they have a patent on some GPL’d code we are shipping. They won’t bother suing small linux vendors, but IBM has lots of money to claim from, that would be worth going to court for. Could they claim only for IBM and not all the little guys who have already been using it?
Is it too much risk to work on the fact that we could always change the code to avoid the patent at a later date?
By Anton Piatek, on December 7th, 2011% This post was originally drafted in May when I actually bought my kindle – I finally got round to actually publishing it…
Earlier this year I finally gave in. I felt a moment of regret about buying into an enormous DRM machine as I clicked purchase on my new Amazon Kindle 3G. I felt a little dirty because of the DRM. Still, I wasn’t buying Sony so I can live with it.
Then theft next day it arrived. So simply packaged, entirely in recycled cardboard, that I forgot about that dirty DRM feeling and tore open the packaging. I pulled out my new kindle and just sat there admiring the instructions showing on the screen. A screen which could show that image for months without charging. It was beautiful.
DRM aside the kindle is an incredible thing.
There are a few hiddenkindle gems including shortcut keys, minesweeper and how to change the screensaver pictures at the following site: From down the hill : Kindle 3 Keyboard Shortcuts et al.
Since then I have been averaging just over a book a month. Some were free, some were £0.71, most are around the £5/£6 mark and one was nearly £10. DRM aside, I have been reading way more than I normally do, as getting to the end of a book is not such an obstacle. The hardest part is choosing what to read next, but while in the middle of a series it is only a 15 second delay to get on to the next book.
I am looking forward to UK lending and eLibraries which support Kindle. Though even without that, I am still reading more than I ever used to and am really loving the fact that I have so much available to read with so little effort. In some ways it is slightly worrying how easy it is to purchase a new book, but at least they are generally cheap.
By Anton Piatek, on December 5th, 2011% I previously wrote about rooting a HTC Desire and installing CyanogenMod 7. A month or so ago, a new CyanogenMod rom was released, and I finally found the time to upgrade it.
Of course I first did a full backup, as described in my previous post, using the recover mod.
I first tried updating the rom via RomManager, which is apparently the preferred way to upgrade CyangonMod roms. Updating the Clockwork Recovery Mod went fine, and the app allows very easy downloading of alternate roms, however actually intalling did not go so well. It failed due to some error in the upgrade script. I decided to simply report the error and move on to a manual upgrade.
Manually updating was pretty much the same as installing the roms in my previous post. Using the reovery mod I installed the new Rom from the zip which was downloaded via RomManager, followed by the Google Aps zip. Then I cleared the Dalvik cache, as I wasnt sure if it would interfere (it doesn’t hurt to clear it anyway).
The update was quite smooth, and after a reboot or two nearly everything was working as before, though it took a while for all the app icons to come back on my desktops. As I did not reset any application data I did not have to reinstall any of my apps or restore the data.
The only issue I found is that the calendar would crash upon starting. I installed CatLog, which allows you to view the android system logs, and very quickly found a stack trace from the calendar app saying it could not find a database column.

I guessed that the storage format must have changed, and as it is all synced from my Google calendar anyway, I thought I would just clear the data and let it resync. Under System->Applications I found the app CalendarStorage, and simply deleted all its data. After a moment to resync from the cloud, everything looks fine.
The latest CyanogenMod 7.1 seems to have some fixes I have been waiting for. In particular, I quite liked the dual lockscreen. A shorter timeout for a swype unlock, where the lockscreen has a music widget. The longer timeout is the unlock pattern. This was not possible in the older CyanogenMod 7.0.3 as a bug seemed to only show the pattern unlock screen.
There is quite a list of new fixes, but I don’t think I needed any of them. One new thing I noticed is that holding down the power button gives not only the usual shutdown/reboot options, but also a screenshot option, which is quite useful and removes the need for a separate app to do this.
|
About All opinions on this blog are my own, and do not reflect the position of any other person, group or entity
|
Recent Comments