• Local sessions
  A local session starts your application when the session is opened. You need 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 and is prevented from exiting while JProfiler is attached to it. 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 application server's framework.
• Applet sessions
  Applet sessions are used for profiling applets with Sun's applet viewer which is shipped with every JDK. You only need to supply the URL to a HTML page containing the applet.

  Note: If the applet view is too restrictive for your applet, please use the Java plugin integration wizard available on the New session tab of the start center.

• Servlet sessions
  JProfiler comes with an integrated Apache Tomcat servlet engine. To quickly profile servlets and Java server pages, you just need to supply the path to the web.xml file associated with your project.

  Note: This session type is for demonstration purposes only. To profile your own installation of Tomcat or other application servers, please use the application server integration wizards available on the New session tab of the start center.

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

• Additional class path
  The session-specific additional class path allows you to enter directories and jar files which are prepended to the default class path (see there for more details on choosing the class path). The class path is also used by the bytecode viewer to find class files for display.
• Additional source path
  The session-specific additional source path allows you to enter directories which are prepended to the default source path (see there for more details on choosing the source 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.
• Additional native library path
  The session-specific native library path allows you to enter directories which are prepended to the default native library path (see there for more details on choosing the native library path). You only need the native library path for loading native libraries with calls to java.lang.System.loadLibrary() or for resolving dependent libraries that have to be dynamically loaded by your native libraries.

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