Broker 10.5 | webMethods Broker Documentation | Administering webMethods Broker | webMethods Broker Command-Line Utilities | Directing Command-line Utilities to Use a Non-Default JRE or JDK
 
Directing Command-line Utilities to Use a Non-Default JRE or JDK
System Requirements for Software AG Products document on the Empower Product Support website lists the JDKs supported by Broker. You can direct Broker command-line utilities to use a non-default JRE or JDK. If you redirect to a non-default JRE or JDK, apply maintenance updates from the appropriate vendor on a regular basis, as you would for JREs and JDKs you install yourself.
If you want to switch to the JDK installed by the installer, it is located in the Software AG_directory \jvm directory.
Important:
On Windows, Broker command-line utilities can only be used with 32-bit JRE or 32-bit JDK.
Note:Software AG tests products only with the JDKs installed by the Software AG Installer. If you redirect products to use a different JDK or JRE and encounter issues, Software AG might require you to reproduce the issues with the JDK that is installed by the Software AG Installer.
*To direct command-line utilities of webMethods Broker APIs for Java and JMS to a Non-Default JRE or JDK
1. Require JDK 1.6.
2. In the step below, command is any command other than awbroker, awbrokermon, server_config, or server_qsck.

webMethods Broker_directory\bin\command -DJAVA_HOME
=JDK_path host:port
On a Windows system, the command might look like this:
C:\SoftwareAG\Broker\bin\broker_status
-DJAVA_HOME=C:\jdk1.6 localhost
On a UNIX system, the command might look like this:
/opt/softwareag/Broker/bin/broker_status
-DJAVA_HOME=/opt/java1.6 localhost