If the session type in the
application settings dialog
is set to "Remote", the following settings are displayed in the middle part of the dialog:
-
Host
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.
-
Port
Choose the port on which the remote 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.
-
Timeout
Choose the timeout in seconds after which JProfiler will give up trying to connect to the
remote application.
-
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 remote 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
remote 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.
previous