Predefined configuration for OpenWebStart

When installing OpenWebStart, several properties can be predefined in a so-called response.varfile file.

Some of the supported properties are lockable. If a property is lockable, you can define an additional property of type PROPERTY_NAME.locked=true to prevent users from editing the property in the user interface. For example, to define a value for the ows.jvm.manager.server.default property that cannot be changed in the user interface, specify the following two properties:

ows.jvm.manager.server.default=https://my.custom.server
ows.jvm.manager.server.default.locked=true

The following table provides an overview of all properties that can be specified in the response.varfile:

property lockable description
ows.jvm.manager.server.default This property must contain a valid URL that defines the server that is used to download new JVMs.
ows.jvm.manager.server.allowFromJnlp Defines if a custom URL can be used to download a JVM. Such URL can be part of a JNLP file.
ows.jvm.manager.vendor Defines a specifc JVM vendor. By doing so, only JVMs from that vendor will be downloaded. You can use ‘*’ to allow any vendor.
ows.jvm.manager.updateStrategy When starting a JNLP application, OpenWebStart can check if an updated JVM is available to run the application. This property defines how OpenWebstart behaves in the JVM check. Possible values are DO_NOTHING_ON_LOCAL_MATCH, ASK_FOR_UPDATE_ON_LOCAL_MATCH and AUTOMATICALLY_DOWNLOAD
ows.update.activated Defines if OpenWebStart should automatically search for updates.
ows.checkUpdate This property has no effect and is only used to lock functionality in the user interface. If this property is locked, a user cannot manually search for OpenWebStart updates.
ows.update.strategy.settings Defines how often OpenWebStart should search for updates when opening the settings windows. Allowed values are ON_EVERY_START, DAILY, WEEKLY, MONTHLY, and NEVER.
ows.update.strategy.launch Defines how often OpenWebStart should search for updates when starting an application. Allowed values are ON_EVERY_START, DAILY, WEEKLY, MONTHLY, and NEVER.
deployment.security.whitelist   A comma seperated list of urls that are defined as whitelist. The whitelist is checked whenever OpenWebStart will download a ressource (like a JAR file).
deployment.assumeFileSystemInCodebase Defines if files from the local filesystem are always handled as if they would be part of the codebase.
deployment.https.noenforce If set to true http urls are not converted to https. Default is false
     

To create a response.varfile file, run the installation of OpenWebStart at least once manually. By doing so a response.varfile file is created in OpenWebStart installation folder in your system. In the installation folder, you find a .install4j folder that contains the basic response.varfile file. The content of such a file looks like this:

sys.adminRights$Boolean=false
sys.fileAssociation.extensions$StringArray="jnlp","jnlpx"
sys.fileAssociation.launchers$StringArray="313","313"
sys.installationDir=/Applications/OpenWebStart
sys.languageId=de

You can easily edit this file and add additional properties based on the table in this article. Do not change the initial content of the file, and add new properties always to the end of the file. After editing, a response.varfile file might look like this:

sys.adminRights$Boolean=false
sys.fileAssociation.extensions$StringArray="jnlp","jnlpx"
sys.fileAssociation.launchers$StringArray="313","313"
sys.installationDir=/Applications/OpenWebStart
sys.languageId=de
ows.jvm.manager.server.default=https://my.custom.server
ows.jvm.manager.server.default.locked=true

If you now use such a file to install OpenWebStart, all the properties will be automatically imported and used at the first start of OpenWebStart.