I would always prefer to use the BLPackage.
- Add the Java binary into BLPackage
- add exertnal command and provide install command in CMD tab
we need 1.5.0 and 1.6.0. 1.6.0 installs fine in a BLPackage with no needs of an external command as we imported it as a custom software with the following install command:
"??SOURCE??" /s INSTALLDIR=c:\java1.6 STATIC=1 WEB_JAVA=0
On the other hand,we have an issue with JDK 1.5.0, no matter if we use a custom software or a file + external command (in both cases into a BLPackage)
We found a solution.
Reporting it here just in case anybody hits the same issue.
It turned out Java JDK 1.5.0 is an InstallShield which embeds an MSI.
The parameters are passed from the InstallShield to the MSI, that's why the double quotes are needed.
By extracting the InstallShield, retrieving the MSI, and directly deploy it we solved the issue.
1) run jdk-1_5_0_22-windows-amd64.exe
2) from the temp dir retrieve the MSI file: J2SE Development Kit 5.0 Update 22.msi
3) import it into BL as MSI package
4) set the install command of the MSI package to
msiexec /I "??SOURCE??" /qn INSTALLDIR=C:\java1.5 ALLUSERS=1 REBOOT=ReallySuppress
1 of 1 people found this helpful
Glad to hear you found a fix for it. Previously when I was faced with an embedded msi package I was able to run the installer against the setup.exe and provide the msi parameters with the /v flag. Maybe this could have been used in your case too.
"setup.exe" /S /v"/qn INSTALLDIR=C:\install_dir ALLUSERS=1 REBOOT=ReallySuppress"