Install WAS Base/ND v6.1.0 on Ubuntu Gutsy.

There are 2 things that need to be configured in order to install WebSphere Application Server Base/ND on Ubuntu Gutsy successfully – tested using WAS Base/ND v6.1.

1 – Ubuntu Gutsy links sh to dash instead of bash. There won’t be any error during the installation of WAS itself, but you will not be able to create any profile, so it’s useless. Two ways to fix this, either remove the symlink and relink it to bash, or change the shebang line inside the WAS install script from #!/bin/sh to #!/bin/bash. Changing the default shell from dash to bash may cause your system slower since dash is lighter than bash, but I think it is hardly noticeable. More info at https://wiki.ubuntu.com/DashAsBinSh.

2 – This applies to WAS ND, I didn’t encounter any issue with Base. If you’re having a problem in getting the dmgr server up, and the error in the SystemOut.log is something like this:

…

[3/12/08 15:38:06:539 MYT] 0000000a LogAdapter E DCSV9403E: Received an illegal configuration argument. Parameter
MulticastInterface, value: 127.0.1.1. Exception is java.lang.Exception: Network Interface 127.0.1.1 was not found in
local machine network interface list. Make sure that the NetworkInterface property is properly configured!
at com.ibm.rmm.mtl.transmitter.Config.<init>(Config.java:238)
at com.ibm.rmm.mtl.transmitter.MTransmitter.<init>(MTransmitter.java:192)
at com.ibm.rmm.mtl.transmitter.MTransmitter.getInstance(MTransmitter.java:406)
at com.ibm.rmm.mtl.transmitter.MTransmitter.getInstance(MTransmitter.java:345)
at com.ibm.htmt.rmm.RMM.getInstance(RMM.java:128)
at com.ibm.htmt.rmm.RMM.getInstance(RMM.java:189)
at com.ibm.ws.dcs.vri.transportAdapter.rmmImpl.rmmAdapter.RmmAdapter.<init>(RmmAdapter.java:218)
at com.ibm.ws.dcs.vri.transportAdapter.rmmImpl.rmmAdapter.MbuRmmAdapter.<init>(MbuRmmAdapter.java:76)
at com.ibm.ws.dcs.vri.transportAdapter.rmmImpl.rmmAdapter.RmmAdapter.getInstance(RmmAdapter.java:133)
at com.ibm.ws.dcs.vri.transportAdapter.TransportAdapter.getInstance(TransportAdapter.java:161)
at com.ibm.ws.dcs.vri.common.impl.DCSCoreStackImpl.<init>(DCSCoreStackImpl.java:178)
at com.ibm.ws.dcs.vri.common.impl.DCSCoreStackImpl.getInstance(DCSCoreStackImpl.java:167)
at com.ibm.ws.dcs.vri.common.impl.DCSStackFactory.getCoreStack(DCSStackFactory.java:92)
at com.ibm.ws.dcs.vri.DCSImpl.getCoreStack(DCSImpl.java:84)
at com.ibm.ws.hamanager.coordinator.impl.DCSPluginImpl.<init>(DCSPluginImpl.java:238)
at com.ibm.ws.hamanager.coordinator.impl.CoordinatorImpl.<init>(CoordinatorImpl.java:322)
at com.ibm.ws.hamanager.coordinator.corestack.CoreStackFactoryImpl.createDefaultCoreStack(CoreStackFactoryImpl
.java:82)

…

Chance is you have not assigned an IP address for your hostname, except for the default 127.* address. If this is the case you won’t be able to federate nodes to the Dmgr as well. So edit your hosts file. Since Edgy the hostname was split to 127.0.1.1, so you will see 127.0.0.1 is assigned to a localhost, and 127.0.1.1 to your hostname. Assign your hostname to 127.0.0.1 as well, and problem solved. But if you plan to do some nodes federation, then assign an IP for your hostname. Your hosts file should look something like this:

127.0.0.1 localhost YourHostName
127.0.1.1 YourHostName

Done.