- System requirements
- Profiler architecture
- Running the profiler
- Profiler activation
- Start profiling
- IDE integration
- Java server integration wizard
- UI integration wizard
- Console integration wizard
- Attach profiler to a running application
- Remote profiling
- Enabling profiling manually
- Startup options
- Connect to profiled application
- Profiling troubleshooting
- Profiling overhead: how to reduce or avoid
- Solving performance problems
- CPU profiling
- Deadlock detector
- Memory profiling
- Garbage collection
- Monitor profiling
- Exception profiling
- Probes: monitor events of various kinds
- Performance Charts
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Summary, snapshot annotation, automatic deobfuscation
- Time measurement (CPU time, wall time)
- Snapshot directory customization
- Export of profiling results to HTML, CSV, XML, plain text
- Profiler Java API
- Profiler HTTP API
- Command line tool to control profiling
- FAQ: How to profile in my scenario?
Console integration wizard
This article describes how to use console wizard to integrate profiler with Java server. Console wizard might be useful if you want to profile remote Java server or the machine has no graphics environment.
See also Java EE high-level profiling.
The wizard enables profiling in a number of popular application servers, generating appropriate startup scripts. Even if your server is not in the list of known servers, the wizard offers the "Other Java application" option which will instruct you on how to manually perform the necessary changes.
Running the wizard
Install profiler on the machine where your Java server is running. License key is not required to use the wizard.
Run the command below:
<Profiler Installation Directory>\bin\integrate.bat
<Profiler Installation Directory>/Contents/Resources/bin/integrate.sh
On other platforms
<Directory with Unpacked Content>/bin/integrate.sh
Follow the instructions that will appear:
The integration wizard will generate output files (copies of configuration files, additional startup scripts) in the directories where original files are located. Please ensure that you run the command with sufficient access rights.
When the server is running with the profiler agent, connect to it from the profiler UI.