Creating Java deployment.config SCCM 2012

Java Deployment Configuration Files and Properties

If you have read the Oracle “Deployment Configuration File and Properties” page on their website you know that you can create a “ System Level” deployment.properties file. This is where a Domain Administrator could centrally manage one system wide deployment.properties file for all PC’s running Java in the enterprise. There are many different properties that could be discussed, however this post is specifically related to my Last Post that discussed Java expiration. So we are interested in the deployment.expiration.check.enabled property referenced in the deployment.properties file.

Java deployment.config File

In order to centrally manage the Java deployment.properties file another file called deployment.config can be created and pushed out to the PC’s on the domain or wherever you need them in the enterprise. The Java deployment.config file has two properties:

1. deployment.system.config
2.deployment.system.config.mandatory

deployment.sytem.config

The deployment.system.config is the URL or File Path to the system wide deployment.properties file. For Example:

deployment.system.config=http\://www.mydomain.com/java/deployment.properties
Or
deployment.system.config=file\:\\\\FileShare\\java\\deployment.properties

The funky looking path is because you have to use an escape character \ when you use a backslash(\) or colon (:).

deployment.system.config.mandatory

The deployment.system.config.mandatory can be set to true or false (=true or =false).

By default the value is false, when set to true IF the deployment.properties file pointed to by the deployment.system.config cannot be found or loaded nothing will be allowed to run.

Simple deployment.config File Example

deployment.system.config=http\://www.mydomain.com/java/deployment.properties
deployment.system.config.mandatory=false

Simple deployment.properties File Example

deployment.expiration.check.enabled=false

So the idea here is to “Point” to the deployment.properties location with the deployment.config file and thereby manage the system wide settings from a single deployment.properties file. The issue now is pushing the deployment.config out to all of the clients. This is easily accomplished in Configuration Manager 2012 by creating a simple package consisting of a batch file and a single deployment.config file as you will see HERE.

Sponsors