CodeMonitor is invoked on the command-line by calling class com.tangentum.CodeMonitor instead of calling the application's main class directly. This way CodeMonitor installs itself as a ClassLoader of the application, and calls the main-method of the application.

From the application's point of view nothing changes. It is invoked through it's main-method and executes normally.

This way the necessary modifications of the application's bytecode is opaque to the application itself, but enables insight of its execution from the outside.

Because there are many different ways to start a Java application, this task can't be reliably automated. Please edit the according batch-scripts, shell-programs, or project-settings to enable CodeMonitor. If you've installed CodeMonitor as recommended, all you have to do is to insert the JAR-file containing CodeMonitor into the application's classpath and invoke com.tangentum.CodeMonitor directly instead of the application's “main” class.

Say you start the application using the standard Java VM as following: java com.myCompany.myApplication. Provided that the JAR-file of CodeMonitor is already included in the classpath, all you have to change is to insert the call to CodeMonitor: java com.tangentum.CodeMonitor com.myCompany.myApplication. This will monitor your application with the configuration file as given in the current directory.

There are some parameters available to CodeMonitor to configure its own execution.