|
51 | 51 | </tr> |
52 | 52 | </table><div class="ind"><a id="GUID-E898FF59-2205-49AA-918A-1C9F792BFC54" name="GUID-E898FF59-2205-49AA-918A-1C9F792BFC54"></a><!-- End Header --> |
53 | 53 | <h1 id="JMCOH-GUID-E898FF59-2205-49AA-918A-1C9F792BFC54" class="sect1">Starting the JDK Mission Control Client</h1> |
54 | | -<div><p>The JMC client executable file is located in the <code>bin</code> directory of the Java SE Development Kit (JDK) installation path (<code>JAVA_HOME</code>).</p> |
55 | | -<div class="p">If the <code>JAVA_HOME/bin</code> directory is in the <code>PATH</code> environment variable, you can start the JMC client by entering <code>jmc</code> at the command-line prompt (shell). Otherwise, you have to specify the full path to the JMC executable:<ul style="list-style-type: disc;"><li><tt>JAVA_HOME\bin\jmc.exe</tt> (Windows)</li> |
56 | | -<li><tt>JAVA_HOME/bin/jmc</tt> (Linux, OS X)</li> |
| 54 | +<div><p>The JMC client executable file is located in the <code>JDK Mission Control Installation</code> directory.</p> |
| 55 | +<div class="p">You can start the JMC client by entering below mentioned path to the JMC Executable at the command-line prompt (shell):<ul style="list-style-type: disc;"><li><tt>INSTALLATION_DIRECTORY\JDK Mission Control\jmc.exe</tt> (Windows)</li> |
| 56 | +<li><tt>INSTALLATION_DIRECTORY/JDK Mission Control/jmc</tt> (Linux, MacOS)</li> |
57 | 57 | </ul> |
58 | 58 | </div> |
59 | | -<div class="infoboxnote" id="GUID-E898FF59-2205-49AA-918A-1C9F792BFC54__GUID-F9E7A833-D515-44CE-B58C-5640AC965EA6"><p class="notep1">Note:</p>On Windows, a shortcut to the JMC client executable is added to the <span class="bold">Java Development Kit</span> folder under <span class="bold">All Programs</span> in the <span class="bold">Start</span> menu.</div> |
60 | | -<div class="infoboxnote" id="GUID-E898FF59-2205-49AA-918A-1C9F792BFC54__GUID-FDFAE1BF-C979-42BB-AFF0-A1126CFA8EA2"><p class="notep1">Note:</p>On OS X, if you cannot find the JMC executable or locate JMC in Spotlight, you can start JMC from the command line using <tt>/Library/Java/JavaVirtualMachines/jdk<span class="italic"><version></span>.jdk/Contents/Home/bin/jmc</tt>. Alternatively, use Finder to browse to <tt>/Library/Java/JavaVirtualMachines/jdk<span class="italic"><version></span>.jdk/Contents/Home/lib/missioncontrol</tt> and double-click the JDK Mission Control app.</div> |
61 | | -<div class="infoboxnote" id="GUID-E898FF59-2205-49AA-918A-1C9F792BFC54__GUID-3D3C37AC-1B49-4A2C-8390-99A9CEEA465D"><p class="notep1">Note:</p>On OS X, when you launch the JMC executable, the Terminal window opens. When you close the JMC client, the Terminal is left behind with the text <code>[Process completed]</code>. To avoid this, open the Terminal <span class="bold">Preferences</span>, then open the <span class="bold">Settings</span> tab, select the scheme you use, then select the <span class="bold">Shell</span> tab, and change the <span class="bold">When the shell exits</span> option to <span class="bold">Close if the shell exited cleanly</span>.</div> |
62 | | -<div class="section"><p class="subhead1">Passing JVM Options To the JMC Launcher</p><p>JMC is a Java application, and the JMC client executable is a launcher for this application. JMC startup is controlled by options specified in the <tt>jmc.ini</tt> file, which is located in the <tt>JAVA_HOME/lib/missioncontrol</tt> directory. Arguments to the <code>-vmargs</code> option in the <code>jmc.ini</code> file are options that are passed to the JVM running the JMC application. You can specify these options to control the way this JVM runs. If you do not want to modify the <code>jmc.ini</code> file, you can specify JVM options on the command line as arguments to the <code>-vmargs</code> option of the <code>jmc</code> command. </p> |
| 59 | +<div class="infoboxnote" id="GUID-E898FF59-2205-49AA-918A-1C9F792BFC54__GUID-FDFAE1BF-C979-42BB-AFF0-A1126CFA8EA2"><p class="notep1">Note:</p>On MacOS, if you cannot find the JMC executable or locate JMC in Spotlight, you can start JMC from the command line using <tt>/INSTALLATION_DIRECTORY/JDK Mission Control.app/Contents/MacOS/jmc</tt>.</div> |
| 60 | +<div class="infoboxnote" id="GUID-E898FF59-2205-49AA-918A-1C9F792BFC54__GUID-3D3C37AC-1B49-4A2C-8390-99A9CEEA465D"><p class="notep1">Note:</p>On MacOS, when you launch the JMC executable, the Terminal window opens. When you close the JMC client, the Terminal is left behind with the text <code>[Process completed]</code>. To avoid this, open the Terminal <span class="bold">Preferences</span>, then open the <span class="bold">Settings</span> tab, select the scheme you use, then select the <span class="bold">Shell</span> tab, and change the <span class="bold">When the shell exits</span> option to <span class="bold">Close if the shell exited cleanly</span>.</div> |
| 61 | +<div class="section"><p class="subhead1">Passing JVM Options To the JMC Launcher</p><p>JMC is a Java application, and the JMC client executable is a launcher for this application. JMC startup is controlled by options specified in the <tt>jmc.ini</tt> file, which is located in the <tt>INSTALLATION_DIRECTORY\JDK Mission Control</tt> directory (Windows and Linux) and <tt>INSTALLATION_DIRECTORY\JDK Mission Control.app\Contents\Eclipse</tt> directory (MacOS). Arguments to the <code>-vmargs</code> option in the <code>jmc.ini</code> file are options that are passed to the JVM running the JMC application. You can specify these options to control the way this JVM runs. If you do not want to modify the <code>jmc.ini</code> file, you can specify JVM options on the command line as arguments to the <code>-vmargs</code> option of the <code>jmc</code> command. </p> |
63 | 62 | <p>To start the JMC client with your own set of JVM options (overriding those specified in the <code>jmc.ini</code> file), run the following command (separate multiple arguments with spaces):</p> |
64 | 63 | <div class="p"><pre class="oac_no_warn" dir="ltr">jmc -vmarg <span class="italic">arguments</span></pre> |
65 | 64 | </div> |
|
0 commit comments