How to configure the system cache

Question

I found that JS2E has this enhancement:
System Cache: Java Web Start now contains both system and user caches. The system administrator can now pre-load applications and shared libraries into the system cache so that multiple users can share the same resources.
Now how exactly do I pre-load applications?

Answer 1

Clearly the documentation of these two subjects needs to be addressed. I will try to get a compete "How to" document posted later in the month, meanwhile:
1.0)Enterprise Configuration Setup
To configure a system or enterprise configuration, you need to create a file called �deployment.config� and put it in the right place. Java Plug-in and Java Web Start will look for this file first in the directory it calls �deployment system home� , and if not found there, will look in lib directory of the JRE you are running Plug-in or Web Start from. The �deployment.system.home� directory is platform dependent. On unix, it is �/etc/.java/deployment�. On Windows it is <windows dir>/Sun/Java/Deployment.
If the file is in deployment.system.home, it will be used by all jres (only valid from 5.0 and up). If the file is not there, but in the lib directory of the jre, it will only be used when that Plugin-in or Web Start are launched from that jre.
The file contains is a java properties file, with only two possible properties in it: deployment.system.config, and deployment.system.config.mandatory. Here are two example deployment.config files:
deployment.system.config=http\://MyCompany.com/deployFiles/deployment.properties
deployment.system.config.mandatory=true
deployment.system.config=file\:/C\:/Program Files/java/jre1.5.0/lib/deployment.properties
deployment.system.config.mandatory=false
Note in both examples, the colon in a properties file must be escaped. This also applies to backslashes themselves in the examples below. This is a common problem.
The first example could be deployed by the admin in deployment.system.home, to require all jres used on this system to load the default and locked properties from the url before launching any Java Plug-in applet or Java Web Start application.
The second example could be deployed with the jre, with both deployment.config and deployment.properties
The deployment.properties file pointed to, can contain any of the properties that can be contained in the users deployment.property file (see list on http://java.sun.com/j2se/1.5.0/docs/guide/deployment/deployment-guide/properties.html). They can also lock properties by listing the property key with �.locked� appended to it. Here is an example system deployment.properties file:
deployment.user.cachedir=D\:\\deployment\\cache
deployment.security.sandbox.awtwarning=false
deployment.security.askgrantdialog.notinca=false
deployment.security.askgrantdialog.notinca.locked
The first two properties are not locked. The use can change to use a different cache location, or turn back on the AWT Warning banner. The last property is locked. The user is not allowed to grant trust to applications who's jars are selfsigned (or signed with any root not in the rootCA certificate store, nor is he allowed to change this setting. The entry in the control panel for this property will be disabled, and any change made to the users deployment.properties file for this property will be ignored.
Now for system cache:
The system cache property is:"deployment.system.cache.dir". It can be set in either an enterprise or users deployment.properties file with:
deployment.user.cachedir=D\:\\deployment\\system\\cache
/Andy