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

JProbe Home > Prodotti > JProbe > Node-Locked Licensing

Stampa

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

JPROBE NODE-LOCKED LICENSING

A node-locked license is essentially a "per named developer" license model. The license is tied to a specific OS type, machine (host name) and named user. The support contact is tied to one designated person.

The following information is required from the customer to generate a license file for a node-locked license:

  • The OS type and hostname of the machine where the application is being analyzed by the JProbe Analysis Engine
  • The hostname of the machine that will be running the JProbe Console

WHAT KIND OF LICENSE DO I NEED - LOCAL OR REMOTE?

The analysis tools in JProbe (Memory, Performance and Coverage) have two distinct components:

  • JProbe Console
    A graphical interface where you can create settings, run your analysis session from, monitor data on your program as it is collected, and review analytics. The Console is used for viewing snapshot files and real-time heap information, as well as for graphically setting Analysis Engine options. This component usually runs on your local desktop machine.
  • JProbe Analysis Engine
    Used for collecting the information from the JVM that your application is running in. This component runs on the machine where your application resides and is usually a remote server.

There are three different configurations that you may perform that, depending on usage, will affect the information that you will need to provide to have your license file generated correctly. Please identify which configuration you plan to work in:

Local Profiling

You are analyzing an application that is local on your desktop. Both the Console and the Analysis Engine are running on the same machine.

Information required for License File generation: host name of machine one and OS type of machine one.

Remote Profiling

You are analyzing 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 (machine two). You will need to install the correct OS version of JProbe on both machines respectively.

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.

Information required for License File generation: Host name of machine one and machine two, and OS type of machine two.

You will need to purchase a license for each unique, individual developer that needs to analyze the application in both local and remote configurations.

Remote Profiling with Terminal Emulation

You are analyzing an application running on a different machine from your desktop. You are using a terminal emulation software package (such as Hummingbird Exceed) on your desktop machine (machine one) and running both the JProbe Console and JProbe Analysis Engine together on the remote machine (machine two). You only need to install JProbe on the remote machine (machine two).

Information required for License File generation: host name of machine two and OS type of machine two.

You will need to purchase a license for each unique, individual developer that needs to analyze the application.

How to obtain a license file:

1. When you have purchased a node-locked version of JProbe, you will be provided with a serial number that you will need to use to obtain your license file.

2. As you install JProbe, you will be asked if you wish to connect directly to Quest Software's licensing site to obtain your license file. By saying yes, the host name of the machine you are installing JProbe on will be sent to the licensing server and will populate a field in the form presented to you. Please verify and correct the hostname as needed.

3. Once all the information has been verified by you, hit submit and the license file will be sent to the e-mail address that was presented in the form.

4. You will have the option of finishing the install for JProbe either with or without the license file; but, you will not be able to run any of the tools in JProbe until this license file has been registered with your local JProbe licensing utility.

Examples

Example 1
Customer needs to analyze both J2EE and stand-alone Java applications that are running on their desktop system. Their local desktop machine is running Windows 2000. The hostname of their machine is "ws000143". This customer needs to purchase a node-locked copy of JProbe, specify OS Type=windows and hostname=ws000143.

Example 2
Customer needs to analyze a J2EE application that is being developed for BEA WebLogic 7.0 running on a Solaris 8.0 machine (named "sol_server_001"). The customer has a Windows XP desktop machine (named "ws003452"). Since the Java application that needs to be analyzed is running on a Solaris system and the client plans to perform the analysis session from their desktop, a Windows system, this is a textbook example of a remote profiling session. This means that the JProbe Console and the JProbe Analysis Engine will be running on different machines. This customer needs to purchase a node-locked copy of JProbe and specify OS Type=Solaris and hostname=sol_server_001 (Analysis Engine location) and hostname=ws003452 (Console location).

Note: again, each unique, individual developer using JProbe requires their own license.

Example 3
Customer needs to analyze an application that is built using IBM WebSphere Application Server running on an AIX server (named "aix_powerhouse1"). Their local desktop is running Exceed on a Windows NT machine (named "wm00123"). Since the Java application is running on an AIX server, we immediately know that OS Type=AIX. If the client chooses to use their Exceed application then the hostname for both the Analysis Engine and Console is the same (name of the AIX machine). So the customer needs to purchase a node-locked license with OS Type=AIX and hostname=aix_powerhouse1 (Analysis Engine and Console location).

Note: again, each unique, individual developer using JProbe through Exceed requires their own license.

Example 4

Customer needs to analyze two applications, one running on a local desktop (NT machine named "jeffs_desktop") and one on a remote server (Solaris server named "solaris1"). Since the Java applications being analyzed are running on both NT and Solaris, the customer will need to purchase two node-locked licenses of JProbe to use JProbe for each application and machine.






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