JPROBE® ARCHITECTURE AND USAGE MODELSJProbe comprises three analysis tools - Memory, Performance and Coverage. Each of these tools has two distinct components: JProbe Console JProbe Analysis Engine
These components may be running on the same computer for local analysis, or on different computers for remote analysis. JProbe Console The JProbe Console provides you with a graphical interface where you can create settings, run your analysis session, monitor data on your program as it is collected, and review analytics. JProbe Analysis Engine The JProbe Analysis Engine collects data on your program as it runs in the JVM. The JProbe Analysis Engine requires a JVM (Java Virtual Machine) with a profiling or tool interface. The interface provides the hooks that the JProbe Analysis Engine uses to analyze the performance of your program. You will need to make sure that the JVM you select fully supports Sun Microsystem’s JVM profiling interface called JVMPI or JVM tool interface called JVMTI. Typical Usage Models Depending on your environment and your development process, your use of JProbe will be one of the following: Local Analysis You analyze an application that is local (on your desktop). Both the JProbe Console and the JProbe Analysis Engine are running on the same machine under the same OS. See illustration. Remote Analysis You analyze an application that is running on a different machine from your desktop. For example, the JProbe Console is running on your desktop (machine one) and the application that you are profiling is running on another machine or remote server (machine two). See illustration. You will need to install the correct OS version of JProbe on both machines respectively. JProbe is licensed by the Analysis Engine OS, the OS where your application is running. Licensing allows you to run the Console on any OS. The most common configuration for remote profiling is when your desktop machine is running a Windows operating system and you are analyzing a remote application built with an Application Server running on a UNIX operating system. Remote Connectivity JProbe works both in NFS (Network File System) and non-NFS environments. NFS Environments When you perform a remote analysis session in an NFS environment, both your Console and your Analysis Engine have access to a shared disk drive that JProbe analysis files are written to and read from. Non-NFS Environments JProbe has a built-in Connection Manager that will automatically transfer JProbe analysis files from the machine running the Analysis Engine to the desktop machine running the Console using the FTP protocal.
|