Process Commander executes within a Java Virtual Machine (JVM) on the server computers that make up the system. (Process Commander does not use Java applets or Java programs that execute on user workstations.)

To learn which JVM is in use on your server node, select > About Process Commander and click the SysInfo button. (You may be prompted for credentials.) VAGUE WHICH CREDENTIALS

The location and identity of the Java JDK and JVM in use is defined through the compiler/compilerPath element of the prconfig.xml system file and appears on the process page of the clipboard. For example:

<env name="compiler/compilerPath" value="f:/jdk1.6./bin/javac.exe" />
<env name="compiler/name" value="javac" />

JVM versions and configuration are important factors in memory performance and overall system throughput. In a production setting on a multiple-CPU system, multiple JVMs support vertical clustering.

Changing to a different JVM version on the server after Process Commander is installed may interfere with the operation of the Clipboard tool. See About the Clipboard tool.

JVM settings can affect performance of your system. For guidance on JVM settings, use the Installation Guide for your platform, and see these Pega Developer Network articles:

• PRKB-21028 Best JVM settings depend on vendor, version, and other factors.
• PRKB-23154 Tuning the IBM JVM 1.4.2 for performance
• PRKB-24141 Tuning the Sun JVM 1.4.2 and 5.0 for performance

	garbage collection, prconfig.xml file, process page, vertical cluster
	Performance checklist

Definitions — J