Packaging Java 6u21
Hi there,
I need to package up jre1.6.0_21 with a custom deployment.properties file. We had a consultant in who did this for v19 and compiled the following deployment.properties:
#deployment.properties
#Tue Apr 13 13:59:54 BST 2010
deployment.version=6.0
deployment.proxy.type=0
deployment.javapi.cache.update=true
deployment.browser.path=C\:\\Program Files\\Internet Explorer\\iexplore.exe
#Java Deployment jre's
#Tue Apr 13 13:59:54 BST 2010
deployment.javaws.jre.0.product=1.6.0_19
deployment.javaws.jre.0.registered=true
deployment.javaws.jre.0.osname=Windows
deployment.javaws.jre.0.platform=1.6
deployment.javaws.jre.0.path=C\:\\Program Files\\Java\\jre6\\bin\\javaw.exe
deployment.javaws.jre.0.location=http\://java.sun.com/products/autodl/j2se
deployment.javaws.jre.0.enabled=true
deployment.javaws.jre.0.osarch=x86
As you can see our main aim is to suppress the use of a proxy and allow direct connection. This needs to roll out with the install we have created using WPS8. The install works but the dep.prop file doesn't seem to go across to the client even though I have included it as a "file" in WPS.
Any ideas of how I can do this?
Thanks
DN
I need to package up jre1.6.0_21 with a custom deployment.properties file. We had a consultant in who did this for v19 and compiled the following deployment.properties:
#deployment.properties
#Tue Apr 13 13:59:54 BST 2010
deployment.version=6.0
deployment.proxy.type=0
deployment.javapi.cache.update=true
deployment.browser.path=C\:\\Program Files\\Internet Explorer\\iexplore.exe
#Java Deployment jre's
#Tue Apr 13 13:59:54 BST 2010
deployment.javaws.jre.0.product=1.6.0_19
deployment.javaws.jre.0.registered=true
deployment.javaws.jre.0.osname=Windows
deployment.javaws.jre.0.platform=1.6
deployment.javaws.jre.0.path=C\:\\Program Files\\Java\\jre6\\bin\\javaw.exe
deployment.javaws.jre.0.location=http\://java.sun.com/products/autodl/j2se
deployment.javaws.jre.0.enabled=true
deployment.javaws.jre.0.osarch=x86
As you can see our main aim is to suppress the use of a proxy and allow direct connection. This needs to roll out with the install we have created using WPS8. The install works but the dep.prop file doesn't seem to go across to the client even though I have included it as a "file" in WPS.
Any ideas of how I can do this?
Thanks
DN
0 Comments
[ + ] Show comments
Answers (13)
Please log in to answer
Posted by:
DocNorton
13 years ago
ORIGINAL: VBScab
The subject of deploying the JRE configuration file(s) has been done to death here on AppDeploy. Search for 'deployment.properties'.
While this may be the case; I already have and didn't find an answer hence posting this.
If anyone else could maybe suggest why the config within the deployment.properties isn't applying I would be very grateful.
Posted by:
timmsie
13 years ago
so are you saying is the file doesn't install, or the settings don't get applied?
Posted by:
anonymous_9363
13 years ago
Timmster:
Sorry, but, as usual on a Friday, the old crystal ball isn't working...
How is your package configured to deploy the file, via a CurrentUser feature linked to a parent feature with an advertised entry-point or via Active Setup? I presume the latter, as I don't recall JRE having any advertised EPs.
What does a verbose log tell you?
the dep.prop file doesn't seem to go across to the client
Sorry, but, as usual on a Friday, the old crystal ball isn't working...
How is your package configured to deploy the file, via a CurrentUser feature linked to a parent feature with an advertised entry-point or via Active Setup? I presume the latter, as I don't recall JRE having any advertised EPs.
What does a verbose log tell you?
Posted by:
DocNorton
13 years ago
ORIGINAL: timmsie
so are you saying is the file doesn't install, or the settings don't get applied?
Both really but the latter due to the former.
My understanding is that if a deployment.properties file is available upon install (which it is - in the package) then it should transfer to the local Java folder within program files.
The package works fine and installs but when I go to check the status of the network settings the proxy settings are still using browser settings.
Thankyou for taking the time to reply...
Posted by:
anonymous_9363
13 years ago
No. That file is meant to be installed either to %SystemRoot%\sun\Java\Deployment or %AppData%\Sun\Java\Deployment. More information can be found here, as directed in the 'Package KB'! :-)
Posted by:
DocNorton
13 years ago
ORIGINAL: VBScab
No. That file is meant to be installed either to %SystemRoot%\sun\Java\Deployment or %AppData%\Sun\Java\Deployment. More information can be found here, as directed in the 'Package KB'! :-)
Many thanks kind sir - will go look :)
Posted by:
pjgeutjens
13 years ago
My understanding is that if a deployment.properties file is available upon install, (which it is - in the package)
just to be clear on this, you speak of making a package with WPS, is this
1) the msi that comes from sun, and is used by the setup.exe
2) an MSI you made yourself that maybe contains and runs the Setup.exe
3) something else...
point I'm making is, are you able to determine wether the "copy the deployment.properties file" functionality is part of the setup stub or the contained msi. I can imagine, if you're bypassing the stub, and it's there that this copy is supported, you might not get the desired result...
PJ
Posted by:
dunnpy
13 years ago
Posted by:
anonymous_9363
13 years ago
Pieter, from what I recall at my last client, neither the stub or the MSI cater for this. I have presumed all along that the OP is using a transform applied to the MSI.
Thinking about it, if the latter is the case and the previous release was the same - and successfully applied the file - the simplest route is to copy the MST, check it for anything that is specific to the last release (unlikely, if it's a simple response transform), edit it accordingly and then apply it.
Thinking about it, if the latter is the case and the previous release was the same - and successfully applied the file - the simplest route is to copy the MST, check it for anything that is specific to the last release (unlikely, if it's a simple response transform), edit it accordingly and then apply it.
Posted by:
pjgeutjens
13 years ago
Ian,
I'm thinking Paul is onto something here, and there's no filecopy per se, just either a user-level or system-level properties file, and if it's supposed to be system level a deployment.config file is needed...
I just got a bit confused with the combination WPS/Package/File supposed to be copied or transferred or whatchacallit
PJ
I'm thinking Paul is onto something here, and there's no filecopy per se, just either a user-level or system-level properties file, and if it's supposed to be system level a deployment.config file is needed...
I just got a bit confused with the combination WPS/Package/File supposed to be copied or transferred or whatchacallit
PJ
Posted by:
DocNorton
13 years ago
ORIGINAL: pjgeutjens
My understanding is that if a deployment.properties file is available upon install, (which it is - in the package)
just to be clear on this, you speak of making a package with WPS, is this
1) the msi that comes from sun, and is used by the setup.exe
2) an MSI you made yourself that maybe contains and runs the Setup.exe
3) something else...
point I'm making is, are you able to determine wether the "copy the deployment.properties file" functionality is part of the setup stub or the contained msi. I can imagine, if you're bypassing the stub, and it's there that this copy is supported, you might not get the desired result...
PJ
The MSI is the one from Sun/Oracle extracted from the exe and I've compiled a transform with WPS.
Posted by:
anonymous_9363
13 years ago
The subject of deploying the JRE configuration file(s) has been done to death here on AppDeploy. Search for 'deployment.properties'.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.