Eclipse: Failed to load the JNI shared library ... vm.dll

I managed to install OSB 11.1.1.4 with OEPE 11.1.16 (oepe-helios-all-in-one-11.1.1.6.1.201010012100-win32.zip) on win7 64-bit. My default JDK is 64-bit. When I fire up Eclipse, I'm getting this "Failed to load the JNI shared library ... vm.dll" error.

Solution is to install JDK 32-bit, then update eclipse.ini to point to your 32-bit JDK. here is the snippet of the .ini file. Keep in mind "-vm option needs to split on 2 lines, and appears before vmargs" (see http://wiki.eclipse.org/Eclipse.ini)
...
--launcher.defaultAction
openFile
-vm
c:\progra~2\java\jdk1.6.0_27\bin\javaw.exe
-vmargs
-Xms256m
-Xmx768m
....

OSB 11.1.1.4 install error: Specified oepe location is not a valid location

I'm re-installing SOA suite 11.1.1.4.

The OSB I have is 11.1.1.4. (ofm_osb_generic_11.1.1.4.0_disk1_1of1.zip)

While installing OSB I encountered this "specified oepe location is not a valid location". However, the location I point to is the matching version 11.1.1.4 OEPE (oepe-galileo-all-in-one-11.1.1.4.0.201001281326-win32).

After struggling for a long time, I downloaded oepe-helios-all-in-one-11.1.1.6.1.201010012100-win32.zip, that did the trick.

I am not sure you see the irony, the matching verion OEPE doesn't work with OSB. I had to use a higher version OEPE 11.1.1.6. oh, well :-(

Jdeveloper extension update

I always ran into issues when updating jdeveloper extensions after a fresh install. The standard steps are: Jdeveloper -> help ->  check for udpates, then select the extensions you need.

Although I don't have proxy, but a popup always asks me to use this proxy "emeacache.uk.oracle.com", I uncheck proxy, the update ended up doing nothing.

It didn't help, their "official" extension center (http://www.oracle.com/ocom/groups/public/@otn/documents/webcontent/131167.xml) doesn't even have the SOA composite editor :(

Well, for today, this is how it is "working" for me: like I said, I do not use proxy from my network to internet, but after numerous failed attempts, i finally logged onto a VPN. It beats me that within the VPN, the update actually worked! Go figure! I'm logging it here, in case, I have to go through the same thing in 6 month again...