Introduction to the Profiling dialog
To begin, switch to a Java-based perspective and look for the green play button profiling dialog icon (). The Profile Configurations profiling dialog is the central launch point for all of the profiling functionality in Rational Application Developer. This may also be accessed from most perspectives by selecting Run > Profile Configurations from the menu.
The Rational Application Developer profiling functionality supports almost all of the standard launch types:
- Eclipse Application
- Java Applet
- Java Application
- Java Unit (JUnit)
- IBM® WebSphere® Application Server Versions 6.0, 6.1, and 7.0 application client
- And others
In addition, support is extended by two profiler-specific types, Attach to Agent and External Java Application:
- Attach to Agent allows any Java virtual machine to be profiled, independent of the use of that JVM by the application, as long as the appropriate JVMTI profiling agent VM arguments are used. Because this entry works with any application, it can be used for otherwise unsupported application configurations, either local or remote, whether they are on an application server or are a full-fledged standalone application. This requires that you configure the appropriate classpath, environment variables, and application parameters from the command line, along with the required JVMTI profiling agent arguments (described later in the tutorial).
- External Java Application, like Attach to Agent, supports profiling any JVM independent of its use. Unlike Attach to Agent, External Java Application requires that you specify the classpath, environment variables, application parameters, and profiling type in the workbench (in the launcher), rather than from the command line. One import point to note: all required class files, Java archive (JAR) files, and additional dependencies must already be present on the target host, because the agent controller does not support the remote file transfer of classes or files to meet the application requirements.