• Local sessions
  A local session starts your application when the session is opened. You have to specify the virtual machine, as well as your application's class path, main class, parameters and working directory. Your application will be started in a separate terminal window. Local sessions are most convenient for profiling GUI and console applications where you have written the main class yourself.
• Remote sessions
  A remote session connects to a running application which has been started with JProfiler's profiling agent. The profiling agent listens on the default port of 8849 which can be changed in the agent's initialization parameters. Remote sessions are most convenient for profiling server applications on remote machines and application servers where you write classes which are loaded and invoked within the framework of the application server.
• Applet sessions
  Applet sessions are used for profiling applets with Sun's applet viewer which is shipped with every JDK. You only have to supply the URL to a HTML page containing the applet.

  Note: If the applet viewer is too restrictive for your applet, please use the Java plugin integration wizard available on the New session tab of the start center to profile the applet directly in the browser.

• Web Start sessions
  JProfiler can profile Java Web Start applications. You only have to supply the URL for the JNLP file or select a cached application.

• Class path
  The class path consists of directories and jar files that are used for the -classpath VM argument. The class path is also used by the bytecode viewer to find class files for display.
• Source path
  The source path optionally lists archives and directories that contain source code for some or all of the entries in the class path. Note that the sources of the selected JDK contained in src.jar or src.zip will be automatically appended if they are installed. The source path is is used by the source code viewer to display Java sources.
• Native library path
  The native library path consists of directories that are added to the native library envrironment variable. The name of the native library envrironment variable depends on the operating system. You only have to specify the native library path when you load native libraries by calling java.lang.System.loadLibrary() or for resolving dependent libraries that have to be dynamically loaded by your native libraries.

When clicking the add button you can select multiple path entries to the path list in one go from the file chooser. Alternatively, to quickly add a list of path entries defined elsewhere, you can copy a path from the system clipboard by clicking copy button. The path must consist of either

• a single path entry
• or multiple path entries separated by the standard path separator (";" on Windows, ":" on UNIX) or by line breaks.

Each path entry can be

• absolute
  The path entry is added as it is.
• relative
  On the first occurrence of a relative path, JProfiler brings up a directory chooser and asks for the root directory against which relative paths should be interpreted. All subsequent relative paths will be interpreted against this root directory.

JProfiler will only add unique path entries into the list. If no new path entry could be found, a corresponding error message is displayed.

Note: Adjusting the class and source path during an active session is effective for the source code and bytecode viewer only.