WebSphere UpdateInstaller Install Problem

... and so it was needed to update my Websphere from 7.0.0.0 to 7.0.0.27. It was all running on AIX 5.3, oh well. Some issues on the way that might suprise WebSphere newcomers follow.

Old java
First, you gotta know, you need an IBM or Sun Java 2. I had java 1.4.2 :-) and was getting various errors, none of them stating it was a wrong version of java. The only common message was the command line output: "lease check for log files in the "updilogs" subdirectory of the current user's home directory...."

Resolution:
To run the install on command line and use the bundled Java, do the following:
./install -options responsefile.updiinstaller.txt -silent -is:javahome /install/was_bonita/JDK/jre.pak/repository/package.java.jre/java/jre


License agreement
Next you might get an error on noc accepting the license. The command prompt says: "Please check for log files in the "updilogs" subdirectory of the current user's home directory. If no logs have been produced there, please try running the install command again, with this additional parameter: -is:javaconsole"

In such case you need to see the log. If the license acceptance is the problem, the following will be shown in the /updilogs/log.txt file:
com.ibm.ws.install.ni.ismp.actions.ISMPWarningDialogAction, wrn, INSTCONFFAILED : LICENSE_NOT_ACCEPTED : Accept the license agreement in the response file before installing.

Resolution: add the license accept option to your response file.
-W silentInstallLicenseAcceptance.value="false"

Migrating Virtualbox image to VMWare

Well... time from time one gets to a situation when he/she has an image in Oracle VirtualBox and needs to use it in VMWare, or other virtualization tools. So did I, trying to migrate my machine set up on VirtualBox to VMWare.

Sounds easy at the beginning:
1] Go to your VirtualBox and select File -> Export Appliance
2] Export the machine as .OVF (not .ova, explained below)
3] wait few hundreds minutes for the export to finish
4] Go to your VMWare Player click Open Virual Machine and select the OVF you created.
5] It tells you "The import failed because *.ovf did not pass OVF specification conformance or virtual hardware compliance checks". Don't worry and hit retry.


Life would be nice if this worked right? But it quite does not. OVF being Open Virtualization Format is described to be a standard. VirtualBox and VMWare can interpret different formats of the file. So you need to do the following:

1. Open the <yourfile>.ovf in your favorite XML editor
2. Find ovf:format parameter in a Disk tag and change it to "http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized"
3. Find any elements describing a SATA disk and change it to SCSI. 
• remember to have instanceId unique within the document
• set lsilogic as resourceSubType
4. make sure all elements called Item under the Section tag have the order of tags:
• Caption
• Description
• InstanceId
• ResourceType
• ResourceSubType
• Address (optional)
• BusNumber(optional)
• example:





5. open command prompt (Start -> cmd.exe) 
• navigate to your VMWare folder 
• usually this way: cd "C:\Program Files (x86)\VMware\VMware Player"
• navigate to OVFTool folder (cd OVFTool)
• run ovftool to generate a VMX file: ovftool your-ovf-file.ovf  new-appliance-vmx
6. if you made the order of tags in the OVF file correct, the process starts running (and it takes some time)
• It might give you some errors... for instance:
• Unsupported element 'ResourceType'
• Missing child element 'InstanceId'
• These errors are caused by a wrong order of tags.
• in such case go to the line with the error and check the order of tags as described in step #4.
• You may also get "OVF hardware element ResourceType with instance ID 5: No support for the virtual hardware device type 20"
• that means you still have a SATA disk specified somehwre in the OVF file
• go back to the OVF file and find all lines containing SATA, change that as described in step #3.
7. Now it should generate a VMX file that you can open in VMWare.

Good luck everybody!