Installing WebSphere Application Server 6.1 on Ubuntu

Rob Harrop

Recently I've been doing some work with a client on WAS 6.1. Since we have a number of Spring users on WAS and I need to test the application, I decided it was time to get a copy of WAS running on one of my work laptops. I say 'one of' because I'm currently working on both my Mac (with OSX) and my ThinkPad (with Ubuntu) - more recently I've just been using the ThinkPad because I can have Oracle XE and WAS running without the need for a VM tool like Parallels. I still prefer the Mac, but to be honest there isn't much difference day-to-day - I just miss some of the more useful Mac tools like Spotlight, Quicksilver, TextMate and NewsFire.

Anyway, back to the main topic - installing WAS 6.1 on Ubuntu. I'm using Ubuntu Edgy and my first attempts at an install failed completely and I just couldn't figure out why. Thankfully a quick Google turned up this article. I was completely unaware that /bin/sh was linked to dash instead of bash - what on earth possessed them. I didn't really like the suggested solution of running the installer, letting it fail and then changing all the scripts in the installed directory. Instead, I just relinked /bin/sh with a quick sudo unlink /bin/sh followed by sudo ln -s /bin/bash /bin/sh. After that, the installer ran like a dream and I was up and running with a WAS install in about 15 minutes.

Even on my ThinkPad with Oracle XE running at the same time, WAS runs pretty quickly. One of the nicest things about WAS is that the tools provided (admin console, command-line tools) are really robust. The Admin Console is noticeable for its performance - many other servers have consoles that are painfully slow.

 

6 responses


  1. I guess it worked, but it would have been safer to just run

    sudo ln -sf bash /bin/sh

    or

    sudo dpkg-reconfigure dash

    , neither of which would have left you with an unbootable system for a short time.

    The rationale for dash is described at https://wiki.ubuntu.com/DashAsBinSh.


  2. Interesting. I installed DB2 9.1 Express-C on a Ubuntu 6.06 VM last week and I noticed a subtle but breaking difference regarding the login shell.

    If I set /bin/bash as login shell for the DB2 user accounts the DB2 admin server doesn't start. But using /bin/sh as login shell it started fine.


  3. We are migrating our project to WAS 6.1 from WAS3.x. The same code is working fine with was3.x but giving NotSerializableException with WAS6.x. I need some favour regading this Exception

    Regards,
    Mahes


  4. [quote comment="13752"]We are migrating our project to WAS 6.1 from WAS3.x. The same code is working fine with was3.x but giving NotSerializableException with WAS6.x. I need some favour regading this Exception

    Regards,
    Mahes[/quote]

    I think this problem is related to your class implementation. WAS is a high available app server, so you must implement all your session classes as Serializable. Try to find every class which is bound to session (HTTP or Stateful SessionBeans) and implement it as serializable, this will solve the problem.


  5. I tried installing WAS 6.1 on my Ubuntu Fiesty 0S, but it says that the OS is not supported. Are you referring to the Community edition ?

    Thanks,
    Atchuth.


  6. One doubt here ::

    From various sites i understand that minimum recomended Sys req for WAS ND 6.1 is AIX 5L 5.2 with Recommended Maintenance package 5200-07 (64-bit kernel support)OR AIX 5L 5.3 with Service Pack 5300-04-01 (64-bit kernel support).

    Now, is it ok to run WAS ND 6.1 on AIX 5L 5.3 5600 which is a higher version than recommended one..pls revert

One trackback

Leave a Reply