The Commandline Tools included with PXE are packaged in two flavors, .sh for use on UNIX (and variants) and .bat for use on Windows systems. In either case, the JAVA_HOME environment variable is expected to be set to the location of a suitable JDK. (See System Requirements for more information.)

Each commandline tool has an associated .cfg file that controls its behavior. (The foo.cfg file controls the foo.sh and foo.bat commands.) Each .cfg file is a Java properties file with the following structure:

• The com.fs.utils.bootstrap.Main.mainClass property is the (real) main class to launch.
• The com.fs.utils.bootstrap.Main.basedir property is the directory from which the library paths are based, relative to the location of the command.
• The com.fs.utils.bootstrap.Main.libs property configures the classpath for the launcher. The list can contain directory names (relative to the base directory) or paths of individual JAR or ZIP files. If /* is appended to a directory name, all of the JAR and ZIP files in that directory are added to the classpath. Without a /*, the directory itself is on the classpath. The various entries are treated in order of appearance.
• The com.fs.utils.bootstrap.system property is a ;-separated or ,-separated list of system properties and values to set.

Be Sure to Escape = in System Property Settings The = between a property name and value in the com.fs.utils.bootstrap.system property should be escaped with a \.

For example, the .cfg file for the version Command is:

com.fs.utils.bootstrap.Main.mainClass=com.fs.utils.license.Version
com.fs.utils.bootstrap.Main.basedir=../
com.fs.utils.bootstrap.Main.libs=pxe-lib/*,lib/*,lib