- Connection details
For a remote connection, you have to enter the host on which the application you want to profile is running either as a DNS name or as an IP address. If this is your local computer, you may enter localhost.
In addition, you have to choose the port on which the profiling agent is listening. If you have not supplied a port parameter, the default port 8849 is the correct choice. This default can be restored by clicking the [Default] button on the right side of the text field for the port.
If the remote host is not directly reachable, you can configure an SSH tunnel by changing "Direct network connection" to "SSH tunnel". In the SSH tunnel wizard, you have a simple mode for configuring an SSH connection to the machine where the profiled JVM is running on. The SSH connection does not require any external executables to be present on your system and supports password and private key authentication.
In cases where you cannot directly connect via SSH to the machine where the profiled JVM is running, you can configure a multi-hop SSH tunnel. Each SSH tunnel hop requires its own authentication. At the end of the SSH tunnel a direct network connection is made to a specified host. This is often the same machine as the target of the last SSH hop, in which case you connect to 127.0.0.1. Here, the context of "localhost" is with respect to the exit of the SSH tunnel and not your local machine where the JProfiler GUI is running.
On the "SSH options" step of the wizard you can choose whether to verify SSH hosts. For the direct SSH connection mode, this is enabled by default and references the file .ssh/known_hosts in your home directory. If you do not havea local SSH installation, you might want to disable host verification. In the multi-hop SSH tunnel mode, verification is disabled by default, because the local known_hosts file may not contain all intermediate hosts.
Alternatively - or in addition to SSH - you can configure a SOCKS proxy for the remote connection.
- Start command
If you enable the "start command" checkbox and enter the path to an executable in the text field to the right, JProfiler will execute this command before trying to connect to the profiled application. The output of that command will be displayed in a terminal window similar to the "local" session type. In this case JProfiler has full control over the life cycle of the profiled application. If the terminal window is closed, the stop button is clicked or JProfiler is exited, the process will be killed if it is still alive.The application server integration wizard uses start commands to make it easy to profile application servers. should you want to take control of the launching of the application server you can temporarily uncheck the "start command" checkbox while preserving the suitable start command.
- Stop command
If you enable the "stop command" checkbox and enter the path to an executable in the text field to the right, JProfiler will execute this command when disconnecting from the profiled application, i.e. when the terminal window is closed, the stop button is clicked or JProfiler is exited.The application server integration wizard uses stop commands where possible.
- Open browser with URL
If you would like to open a browser window along with the session, please select this checkbox and enter the URL in the adjacent text field. JProfiler polls this URL until it becomes available, only then is the browser opened. Please set the browser start command if you're working on a UNIX platform. - Connection timeout
Choose the timeout in seconds after which JProfiler will give up trying to connect to the profiled application.
 | The [config synchronization options] button brings up the config synchronization options dialog. |