Quest Software Inc.
Carrello | Come acquistare | Log in | White Papers | Download | Cerca

JProbe Home > Prodotti > JProbe > Architecture and Usage

Stampa

Richiedi offerta Invia per e-mail
Panoramica
Caratteristiche e benefici
Informazioni sulla release
Documenti
Webcast ed eventi
Download software
Shop JProbe
JProbe

JPROBE® ARCHITECTURE AND USAGE MODELS

JProbe 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.


 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 






Come procedere
Come procedere
View a product demo
Consulta le brochure
Scarica i white paper
Read a tech brief
Leggi i case study
Partecipa agli eventi
Download software

Shop JProbe
Download the JProbe Trial
JProbe in Action

View a product demo

This flash demo follows the same workflow as the JProbe live weekly webcast.

Visit the JProbe Community

Interact, collaborate, and share knowledge in an interactive forum with JProbe customers, prospective customers, and all Java performance enthusiasts. Click here.

Speak with a Sales Representative

Request Additional Info

Use this link to request that a Sales Rep contact you.

Related Solutions

PerformaSure complements JProbe with robust, multi-tier Java transaction profiling: easily isolate, diagnose and resolve application performance problems across the Java technology stack at both the integration and load testing phases of the application lifecycle in pre-production.

        © Quest Software, Inc. All rights