Unattended installs with Installshield Java Edition
Hello all. Been visiting a long time for help, but never found the need to register till now.
I'm working on creating an installation packge for Teamcenter Catia Manager. It is an InstallShield Java Edition installation using a .exe launcher.
I've been using these two pages as references.
http://helpnet.acresso.com/robo/projects/IS10-5UniversalHelpLibrary/topics/commandline_options_run.htm
http://helpnet.acresso.com/robo/projects/IS10-5UniversalHelpLibrary/topics/commandline_options_launchers.htm
I'm trying to create a response file to this installation so that it can be pushed silently. So far I've had no luck using the standard -r switch on the exe to make an iss file, nor have I been able to use -options-record either. I tried to extract files from the exe so that I could work with the .jar file directly, but when I use the is:extract I get an error message about DiskSpaceCheck ==> unable to locate path. I also tried to find the extracted files in the temp dir during the application installation but was unable to find them there as well.
Anyone have any experience working with an exe launched java installation and setting it up for unattended installation?
I'm working on creating an installation packge for Teamcenter Catia Manager. It is an InstallShield Java Edition installation using a .exe launcher.
I've been using these two pages as references.
http://helpnet.acresso.com/robo/projects/IS10-5UniversalHelpLibrary/topics/commandline_options_run.htm
http://helpnet.acresso.com/robo/projects/IS10-5UniversalHelpLibrary/topics/commandline_options_launchers.htm
I'm trying to create a response file to this installation so that it can be pushed silently. So far I've had no luck using the standard -r switch on the exe to make an iss file, nor have I been able to use -options-record either. I tried to extract files from the exe so that I could work with the .jar file directly, but when I use the is:extract I get an error message about DiskSpaceCheck ==> unable to locate path. I also tried to find the extracted files in the temp dir during the application installation but was unable to find them there as well.
Anyone have any experience working with an exe launched java installation and setting it up for unattended installation?
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
joedown
16 years ago
Have you tried the /r to record a setup file? If one gets recorded it will be in the Windows directory. I've noticed that the extract option does not always work but this is the format "MainSetup.exe -extract_all:<some path>"
Posted by:
anonymous_9363
16 years ago
ORIGINAL: sneedniNo, sorry, I don't. I always capture these puppies, as I always like to know what they're unleashing on my patiently-built build.
Anyone have any experience working with an exe launched java installation and setting it up for unattended installation?
Posted by:
sneedni
16 years ago
ORIGINAL: joedown
Have you tried the /r to record a setup file? If one gets recorded it will be in the Windows directory. I've noticed that the extract option does not always work but this is the format "MainSetup.exe -extract_all:<some path>"
The regular /r doesn't work. Says its not a supported option.
ORIGINAL:VBScab
No, sorry, I don't. I always capture these puppies, as I always like to know what they're unleashing on my patiently-built build.
Yeah, I tried to do a recapture but its arguing with me quite a bit about a java plug in not being installed properly when I both compile and run the msi.
Posted by:
anonymous_9363
16 years ago
ORIGINAL: sneedniThe Java thing is a well-known "gotcha" which you can bypass by determining which JRE the application requries (i.e. EXACTLY which flavour...) and installing it before you capture.
Yeah, I tried to do a recapture but its arguing with me quite a bit about a java plug in not being installed properly when I both compile and run the msi.
If you want to keep what you have already, you can probably bypass the registration errors by ensuring that the JRE junk - principally NPJAVA*.DLL - doesn't appear in the MSI's SelfReg table. These files fool the COM extraction employed by your authoring tool because they have the DLLRegisterServer entry-point but no COM information.
Posted by:
reds4eva
16 years ago
Strangely enough Im doing a similar package at the moment, Sybase. It has both 142_13 and 142_06 Java.
Im guessing (more than guessing) you are getting 1904, module failed to register errors ?
Just do what VBScab said, remove the entries from the Selfreg table, and use Wisecomcapture to create reg files to import the com info into the MSI, if they have com info. Or, install the Java versions before capture.
Im guessing (more than guessing) you are getting 1904, module failed to register errors ?
Just do what VBScab said, remove the entries from the Selfreg table, and use Wisecomcapture to create reg files to import the com info into the MSI, if they have com info. Or, install the Java versions before capture.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.