This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: Unix Command Line Installer - JVM path?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 29, 2012
07:59 AM
Unix Command Line Installer - JVM path?
Greetings
I thought the JVM search path settings in the install config were used as search path to run installer, but perhaps I'm not reading the documentation correctly.
"The search list is used by the installer when determining whether a compatible VM is found on the system. It is NOT used by LaunchAnywhere when looking for a VM to run the application"
So I'm not sure if "the application" is a Launch Anywhere created by me, or if "the application" is the installer application.
So even if I have, for example /usr/java/6/jre/bin/java in the search path under "search panel settings", when you first invoke install.bin, unless this is in the user's $PATH, the installer will not load.
Is there a way to programmatically look in the standard locations for the JVM? Do I need to set LAX_VM in the installer?
Thanks!
Jan
I thought the JVM search path settings in the install config were used as search path to run installer, but perhaps I'm not reading the documentation correctly.
"The search list is used by the installer when determining whether a compatible VM is found on the system. It is NOT used by LaunchAnywhere when looking for a VM to run the application"
So I'm not sure if "the application" is a Launch Anywhere created by me, or if "the application" is the installer application.
So even if I have, for example /usr/java/6/jre/bin/java in the search path under "search panel settings", when you first invoke install.bin, unless this is in the user's $PATH, the installer will not load.
Is there a way to programmatically look in the standard locations for the JVM? Do I need to set LAX_VM in the installer?
Thanks!
Jan
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 30, 2012
12:24 AM
Hi,
The Search path should be just /usr/java/6/jre/bin or /usr/java/6/jre or /usr/java/6 since(and if) the java executable patterns are java, bin/java and jre/bin/java.
Try this and let us know if it works
Thanks.
The Search path should be just /usr/java/6/jre/bin or /usr/java/6/jre or /usr/java/6 since(and if) the java executable patterns are java, bin/java and jre/bin/java.
Try this and let us know if it works
Thanks.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 30, 2012
11:59 AM
Thanks! I figured out that I needed to change the installer settings to allow user to select the JVM.
Interesting discovery, though - we found that the installer hangs with Java SE 5, and IA Requirements state Java6+, however it defaults to allow Java5 in the search path 🙂
Interesting discovery, though - we found that the installer hangs with Java SE 5, and IA Requirements state Java6+, however it defaults to allow Java5 in the search path 🙂
RamyaVenkatesh wrote:
Hi,
The Search path should be just /usr/java/6/jre/bin or /usr/java/6/jre or /usr/java/6 since(and if) the java executable patterns are java, bin/java and jre/bin/java.
Try this and let us know if it works
Thanks.
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)