Remote profiling is the case when the profiled application and the profiler UI run on different machines, usually on a server and your developer machine correspondingly.
See also Local profiling.
To profile remote application you have to do two things:
There are 3 options to load the profiler agent into JVM:
Use remote profiling from user interface if you have SSH access to the remote machine. The profiler will transfer all necessary files to the remote computer and will attach the agent to a running JVM.
Start JVM with the profiler agent by applying the console Java EE server integration wizard on the remote machine or enable profiling manually. We recommend to start JVM with the agent, because attaching the agent to a running JVM has limitations in profiling functionality and is not always possible.
Run the console attach wizard on the remote machine.
When the remote application is running, connect to it from the profiler UI to perform profiling.
If connection fails, please refer to the troubleshooting instructions.