+JavaInspect can be controlled in 2 different ways:
+</p>
+<ul class="org-ul">
+<li><a href="#sec-3-1">as standalone commandline utility</a>
+</li>
+<li><a href="#sec-3-2">as embedded Java library via Java API</a>
+</li>
+</ul>
+</div>
+
+<div id="outline-container-sec-3-1" class="outline-3">
+<h3 id="sec-3-1"><a id="ID-acf1896a-74b4-4914-acf6-a77075e07f25" name="ID-acf1896a-74b4-4914-acf6-a77075e07f25"></a><span class="section-number-3">3.1</span> usage as commandline utility</h3>
+<div class="outline-text-3" id="text-3-1">
+<p>
+To enable commandline support, (study and) execute script:
+</p>
+<pre class="example">
+commandline launcher/install
+</pre>
+
+<p>
+Warning: It was tested only on Debian Stretch linux.
+</p>
+
+<p>
+Available commandline arguments:
+</p>
+<p class="verse">
+-j (existing files)…<br >
+    JAR file(s) to render.<br >
+<br >
+-n (mandatory, string)<br >
+    Graph name.<br >
+<br >
+–debug<br >
+    Show debug info.<br >
+<br >
+-k<br >
+    Keep dot file.<br >
+<br >
+-h<br >
+    Hide orphaned classes.<br >
+<br >
+-w (one to many strings)…<br >
+    Whitelist glob(s).<br >
+<br >
+-b (one to many strings)…<br >
+    Blacklist glob(s).<br >
+<br >
+-d (existingdirectory)<br >
+    Target directory. Default is current directory.<br >
+<br >
+-t (options: png, svg)<br >
+    Target image type. Default is: svg.<br >
+</p>
+</div>
+</div>
+<div id="outline-container-sec-3-2" class="outline-3">
+<h3 id="sec-3-2"><a id="ID-bbeeffc8-3767-440d-8d93-ec9124dd60ee" name="ID-bbeeffc8-3767-440d-8d93-ec9124dd60ee"></a><span class="section-number-3">3.2</span> usage via Java API</h3>
+<div class="outline-text-3" id="text-3-2">
+<p>
+Requires that classes to be visualised are available in the classpath.
+</p>
+
+<p>
+To get JavaInspect into same classpath with your projecs I so far came
+up with 2 solutions:
+</p>
+
+<ol class="org-ol">
+<li>Add JavaInspect library in your project as a dependency.
+</li>
+
+<li>Create new Java project for the purpose visualizing your other
+projects and include JavaInspect and your projecs binary artifacts
+(Jar's) into new project classpath. Built binary Jar's (with no
+source code) are sufficient because JavaInspect operates via
+reflection.
+</li>
+</ol>
+
+<p>
+Simple Java based control/configuration code needs to be written for
+each project. I usually put such code into directories devoted for