When you close the session, you can save the session settings (filter, profiling and triggers settings) so that you can reuse them for future use. When you attach to the same application again, start the saved session instead of using "Quick attach". Of course you can also start out by creating such a dedicated session in the first place.
In your local JProfiler GUI, create an "Attach to profiled JVM (local or remote)" session and enter the host name and the same profiling port that you specified in jpenable on the remote machine. In addition, you can configure an SSH tunnel and a SOCKS proxy. When you start the session, it connects to the remote JVM and you can start profiling.
Alternatively, invoke Session->Quick Attach and select the "On another computer" option that will allow you to enter your remote connection details without configuring a session. When you close the session, you will then be asked whether to save it or not.
If you wish to set the displayed name yourself, for example because you have several processes with the same main class that would otherwise be undistinguishable, you can set the VM parameter -Djprofiler.displayName=[name]. If the name contains spaces, use single quotes: -Djprofiler.displayName='My name with spaces' and quote the entire VM parameter with double quotes if necessary. In addition to -Djprofiler.displayName JProfiler also recognizes -Dvisualvm.display.name.
When you choose "Dynamic instrumentation" as the method call recording type, it is important to choose profiled packages that focus on the classes of interest. In that way, relatively few classes are instrumented. Alternatively, you can choose Sampling in the profiling settings.
If JProfiler detects that the PermGen space would be overloaded with the current filter settings, it will warn you in the session startup dialog. You should then switch to sampling or define narrow set of profiled packages. Clicking on the hyperlinks in the warning message will quickly make these changes. When selecting profiled packages, the total amount of instrumented classes is monitored and you are notified if you exceed the approximate maximum number of classes that can be instrumented.
By default, array allocations are not recorded in attach mode, although the session startup dialog gives you the possibility to do so for "non-client" JVMs (the "client" JVM has a bug that prevents this from working successfully).