Problem with "enterprise" (system) deployment
We are setting-up an "enterprise configuration" of JWS where we want JWS applications installed under the system folder (e.g. "\Sun\Java\Deployment") rather the user "Documents and Settings" folder. The install script will run on thousands of desktops the same day. Since we do want the JAR files downloaded to all these desktops at the same time, the script does not run "javaws -import" at the end - it simply copies the files deployment.properties and deployment.config under the sysem folder with the following properties set:
deployment.system.security.trusted.certs = C\:\\WINDOWS\\Sun\\Java\\Deployment\\keystore.jks
deployment.system.cachedir = C\:\\WINDOWS\\Sun\\Java\\Deployment\\cache\\
deployment.system.config = file:\\C:\\WINDOWS\\Sun\\Java\\Deployment\\deployment.properties
deployment.system.config.mandatory = true
The install script also copies a shortcut with the target "jawaws -system...."
This setup works fine and the shortcut does cause the application to be downloaded at the proper system location.
However, if the user starts the app from IE (e.g. http://xx.xx.jnlp), it ignores the system configuration and downloads the app to the local user folder.
Is there anyway to force the download to occur in the system folder ? What I find pretty odd is that even lanuched from IE, JWS does read the deployment.properties and deployment.config files from the system folder. I've put a typo and it there and JWS complained right away.