Hi there,
We are trying to package/automate the Find Local button.
Given it's an EXE and not an MSI or such, we are struggling to package the install for our users in such a way that it auto-presses the Find Local button during the installation.
OpenWebStart - How to package/automate the Find Local button
The JRE will be installed prior to this, so will be present on the machine - but currently it's a manual step for our users to press that button. We are hoping for a better way to do so.
We could not find a regkey or installation switch/statement that makes it work.
Anyone know how?
Thank you!
B
OpenWebStart - How to package/automate the Find Local button
OpenWebStart - How to package/automate the Find Local button
- Attachments
-
- OpenWebStart - Find Local Button.png (46.36 KiB) Viewed 29 times
-
Janak Mulani
- Posts: 1152
- Joined: 24 Mar 2020, 13:37
Re: OpenWebStart - How to package/automate the Find Local button
Hi,
OWS installer installs two exes: javaws.exe and itw-setting.exe.
It is the itw-settings.exe that allows you to manage the JVMs used by OWS when launching the Jnlp application.
What is your exact requirement with respect to the JVM used by OWS to run the Jnlp application?
Please see https://openwebstart.com/docs/OWSGuide. ... management.
OWS can automatically download the JRE that best matches the one required to run the application as specified in the Jnlp file.
OWS installer installs two exes: javaws.exe and itw-setting.exe.
It is the itw-settings.exe that allows you to manage the JVMs used by OWS when launching the Jnlp application.
What is your exact requirement with respect to the JVM used by OWS to run the Jnlp application?
Please see https://openwebstart.com/docs/OWSGuide. ... management.
OWS can automatically download the JRE that best matches the one required to run the application as specified in the Jnlp file.
Re: OpenWebStart - How to package/automate the Find Local button
Hi Janak,
The problem is, we are dependant on some specific older JRE's for some old legacy websites that need those older versions specifically.
Therefore, if we were to automatically download the JRE, it would only get the latest one I had thought.
Without opening the App itself, is there no way to package the installation in such a way that the first time it opens, it runs/presses "Find Local" automatically?
The problem is, we are dependant on some specific older JRE's for some old legacy websites that need those older versions specifically.
Therefore, if we were to automatically download the JRE, it would only get the latest one I had thought.
Without opening the App itself, is there no way to package the installation in such a way that the first time it opens, it runs/presses "Find Local" automatically?
-
Janak Mulani
- Posts: 1152
- Joined: 24 Mar 2020, 13:37
Re: OpenWebStart - How to package/automate the Find Local button
Please have a look at https://openwebstart.com/docs/OWSGuide.html > Configuration Properties Overview
There are ows.jvm.* properties which can be predefined at the time of installation in the response.varfile (https://openwebstart.com/docs/OWSGuide.html). Otherwise, they can be specified manually in the <USER_HOME>\.config\icedtea-web\deployment.properties file
The following properties can be helpful to you:
There are ows.jvm.* properties which can be predefined at the time of installation in the response.varfile (https://openwebstart.com/docs/OWSGuide.html). Otherwise, they can be specified manually in the <USER_HOME>\.config\icedtea-web\deployment.properties file
The following properties can be helpful to you:
Code: Select all
ows.jvm.manager.searchLocalAtStartup : If set to true, OpenWebStart will search for new local JVMs at every start. Default is false.
ows.jvm.manager.excludeDefaultSearchLocation : If set to true OpenWebStart will exclude the default locations when searching for JVMs. Default is false.
ows.jvm.manager.customSearchLocation : Comma separated list of custom locations to search for JVMs. Default is empty.