Java deployment.properties issues
Anyone knows all about Java deployment?
My customer wants to add a runtime parameter to a specific Java version in the Java console.
I've found the information in the deployment.properties in the user-profile.
Now I want to know if there's a possibility to pass this as an argument to the installer, or otherwise sort this without scripting it?
This is how the deployment.properties file looks.
Note! There are side-by-side installations of Java on the machines.
The problem with scripting this would be that (if my assumptions are correct), if/when next version of Java is installed the 0, 1, 2 in the text above will change so the latest version is always 0.
So, I would need to first check what number the Java version have (in my case 0 for jre 1.6.0_30)
Then add -Xmx256m to the row "deployment.javaws.jre.0.args="
My question is:
Is there an easy way to do this?
Anyone done it? How?
My customer wants to add a runtime parameter to a specific Java version in the Java console.
I've found the information in the deployment.properties in the user-profile.
Now I want to know if there's a possibility to pass this as an argument to the installer, or otherwise sort this without scripting it?
This is how the deployment.properties file looks.
#deployment.properties
#Thu Mar 08 15:55:02 CET 2012
deployment.javaws.cache.update=true
deployment.version=6.0
deployment.capture.mime.types=true
deployment.javapi.cache.update=true
deployment.browser.path=C\:\\Program Files\\Internet Explorer\\IEXPLORE.EXE
#Java Deployment jre's
#Thu Mar 08 15:55:02 CET 2012
deployment.javaws.jre.1.location=http\://java.sun.com/products/autodl/j2se
deployment.javaws.jre.0.args=
deployment.javaws.jre.0.registered=true
deployment.javaws.jre.2.enabled=true
deployment.javaws.jre.1.args=
deployment.javaws.jre.1.enabled=true
deployment.javaws.jre.2.args=
deployment.javaws.jre.2.platform=1.5
deployment.javaws.jre.1.registered=true
deployment.javaws.jre.2.osname=Windows
deployment.javaws.jre.2.osarch=x86
deployment.javaws.jre.0.osarch=x86
deployment.javaws.jre.0.osname=Windows
deployment.javaws.jre.2.location=http\://java.sun.com/products/autodl/j2se
deployment.javaws.jre.1.product=1.6.0_20
deployment.javaws.jre.2.registered=true
deployment.javaws.jre.0.platform=1.6
deployment.javaws.jre.0.path=C\:\\Program Files\\Java\\jre1.6.0_30\\bin\\javaw.exe
deployment.javaws.jre.0.location=http\://java.sun.com/products/autodl/j2se
deployment.javaws.jre.1.path=C\:\\Program Files\\Java\\jre6\\bin\\javaw.exe
deployment.javaws.jre.0.enabled=true
deployment.javaws.jre.2.path=C\:\\Program Files\\Java\\jre1.5.0_12\\bin\\javaw.exe
deployment.javaws.jre.1.osarch=x86
deployment.javaws.jre.1.osname=Windows
deployment.javaws.jre.2.product=1.5.0_12
deployment.javaws.jre.1.platform=1.6
deployment.javaws.jre.0.product=1.6.0_30
Note! There are side-by-side installations of Java on the machines.
The problem with scripting this would be that (if my assumptions are correct), if/when next version of Java is installed the 0, 1, 2 in the text above will change so the latest version is always 0.
So, I would need to first check what number the Java version have (in my case 0 for jre 1.6.0_30)
Then add -Xmx256m to the row "deployment.javaws.jre.0.args="
My question is:
Anyone done it? How?
0 Comments
[ + ] Show comments
Answers (0)
Please log in to answer
Be the first to answer this question
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.