Moving Web GUI from one machine to another

Having spent a merry 6 hours installing OMNIbus WebGUI on a VM, I decided it would be better off on a physical machine. This is of course a very silly thing to think, and it was bound to go wrong. Furthermore it is completely unsupported behaviour and I would not suggest following this for any kind of production scenario. For one thing it would completely confuse any installer setup you have, so would not allow the installation of anything else on top of the migrated machine.

Once tarred and copied (basically everything from the install directory downwards) I did a quick grep through to look for configurations that might need to change. It boiled down to 3 files (four if you copied the objectserver over as well):

1. ./tipv2/properties/objectserver.properties
2. ./netcool/omnibus_webgui/etc/datasources/ncwDataSourceDefinitions.xml
3. ./tipv2/profiles/TIPProfile/config/cells/TIPCell/wim/config/wimconfig.xml

Just open those, and do a search/replace for the old/new IP address. If you've copied over the object server as well, you'll need to update the omni.dat file, then re-run nco_igen

Enabling local network traffic on Ubuntu

My local network consists of an NSLU2 (Slug), a printer and my router. I have made the considered conclusion that it is not going to cause much of an attack vector. My work enforced iptables disagrees, but fiddling with iptables scares me. Luckily I have found ufw, which makes life just *so* much easier: sudo apt-get install ufw sudo ufw enable sudo ufw default deny sudo ufw allow 192.168.1.0/24 Hey presto, I can see my local network. Life is good.