Previous | Next | See Also
Some features described here are available in Ultimate edition only.

Use this dialog to create or edit run/debug configurations for JSR45-compatible application servers.

Generally, you may want to use this type of run/debug configuration under the following conditions:

On this page:

Server tab

ItemLocal/RemoteDescription
Application ServerBoth Select the server configuration to be used.

If the run/debug configuration is intended for working with a remote server, the same server version should be configured locally and associated with the run/debug configuration.

Click Configure to create a new server configuration or edit an existing one. (The Application Servers dialog will open.)

Start browserBothSelect this check box to run the default Web browser to study your application output there.
With JavaScript debuggerBoth If this check box is selected, the Web browser is started with the JavaScript debugger enabled.

JavaScript debugging is available for Firefox only. Note that when you debug your JavaScript in Firefox for the first time, the JetBrains Firefox extension will be installed.

Startup pageBothIn this field, specify the URL the browser should go to when started. In most typical cases, this URL will correspond to the root of your Web application or its starting page.
VM optionsLocalIf necessary, specify the command-line options to be passed to the server JVM at the server start.

If you need more room to type, click shift-enter-button next to the field to open the VM Options dialog where the text entry area is larger.

When specifying the options, follow these rules:

  • Use spaces to separate individual options, for example, -client -ea -Xmx1024m.
  • If an option includes spaces, enclose the spaces or the argument that contains the spaces in double quotes, for example, some" "arg or "some arg".
  • If an option includes double quotes (e.g. as part of the argument), escape the double quotes by means of the backslashes, for example, -Dmy.prop=\"quoted_value\".
On 'Update' actionLocalSelect the action to be performed when the application is updated in the Run or the Debug tool window (updaterespath).
Show dialogLocal Select this check box if you want to see the Update <application name> dialog every time you perform the Update action.

The Update <application name> dialog is used to view and change the current update option (for example, Restart server) prior to actually updating the application.

JSP's packageBothSpecify the Java package prefix to be used for jsp-to-servlet translation.
VM options variableLocalIf there is a variable which stores the command-line JVM options, you can specify the name of this variable in this field. In this way, you can pass the corresponding options to the server JVM at the server start.
PortBothSpecify the HTTP server port.
Use JSP's line mapping model specific for WebSphere 5.1BothIf the run/debug configuration is intended for working with WebSphere Server 5.1, select this check box to be able to debug your JSPs.

(To be able to debug JSPs, it’s necessary to maintain relationships between the lines of the source files and the corresponding positions in the compiled code. All the servers except WebSphere 5.1 form such relationships similarly.)

HostRemoteThe DNS name or the IP address of the server host (for example, localhost, 127.0.0.1, etc.).

Logs tab

Use this tab to specify which log files generated while running or debugging should be displayed in the console, that is, on the dedicated tabs of the Run or Debug tool window.

ItemDescription
Is ActiveSelect check boxes in this column to have the log entries displayed in the corresponding tabs in the Run tool window or Debug tool window.
Log File EntryThe read-only fields in this column list the log files to show. The list can contain:
  • Full paths to specific files.
  • Ant patterns that define the range of files to be displayed.
  • Aliases to substitute for full paths or patterns. These aliases are also displayed in the headers of the tabs where the corresponding log files are shown.

    If a log entry pattern defines more than one file, the tab header shows the name of the file instead of the log entry alias.

Skip ContentSelect this check box to have the previous content of the selected log skipped.
Save console output to fileSelect this check box to save the console output to the specified location. Type the path manually, or click the browse button and point to the desired location in the dialog that opens.
Show console when standard out changesSelect this check box to activate output console and bring it forward, if associated process writes to Standard.out.
Show console when standard error changesSelect this check box to activate output console and bring it forward, if associated process writes to Standard.err.
add Click this button to open the Edit Log Files Aliases dialog where you can select a new log entry and specify an alias for it.
edit1Click this button to edit the properties of the selected log file entry in the Edit Log Files Aliases dialog.
deleteClick this button to remove the selected log entry from the list.
browseButton.png Click this button to edit the select log file entry.

The button is available only when an entry is selected.

Code Coverage tab

Use this tab to configure code coverage monitoring options.

Note that this tab is not available for remote servers.

ItemDescription
Choose code coverage runnerSelect the desired code coverage runner.
SamplingSelect this option to measure code coverage with minimal slow-down.
TracingSelect this option to collect accurate branch coverage. This mode is available for the IntelliJ IDEA code coverage runner only.
Track per test coverageSelect this check box to detect lines covered by one test and all tests covering line.
Packages and classes to record code coverage dataIf necessary, specify the classes and packages to be measured.

Use add-class or add-package to add classes or packages to the list.

To remove the classes or packages from the list, select the corresponding list items and click delete.

Enable coverage in test folders.Select this check box to include the test source folders in code coverage analysis.

Startup/Connection tab

ItemLocal/RemoteDescription
run Run 
 debug Debug		 Both Select Run or Debug to show settings either for the run or the debug mode.
runWithCoverage Run with CoverageLocalSelect Run with Coverage to show settings for run with coverage mode.
Startup scriptLocal Specify the script to be used to start the server. If necessary, you can also specify the script parameters and the options to be passed to the server JVM.

You can provide all the necessary information right in the field, by typing. As an alternative:

  • To specify the script, click browseButton and select the desired script in the dialog that opens.
  • To specify the parameters, click shift-enter-button and specify the script parameters and VM options in the Configure VM and Program Parameters dialog.

    When specifying the parameters and options, follow these rules:

    • Use spaces to separate individual parameters and options, for example, -client -ea -Xmx1024m.
    • If a parameter or an option includes spaces, enclose the spaces or the argument that contains the spaces in double quotes, for example, some" "arg or "some arg".
    • If a parameter or an option includes double quotes (e.g. as part of the argument), escape the double quotes by means of the backslashes, for example, -Dmy.prop=\"quoted_value\".
Shutdown scriptLocal Specify the script to be used to stop the server. If necessary, you can also specify the script parameters and the options to be passed to the server JVM.

You can provide all the necessary information right in the field, by typing. As an alternative:

  • To specify the script, click browseButton and select the desired script in the dialog that opens.
  • To specify the parameters, click shift-enter-button and specify the script parameters and VM options in the Configure VM and Program Parameters dialog.

    When specifying the parameters and options, follow these rules:

    • Use spaces to separate individual parameters and options, for example, -client -ea -Xmx1024m.
    • If a parameter or an option includes spaces, enclose the spaces or the argument that contains the spaces in double quotes, for example, some" "arg or "some arg".
    • If a parameter or an option includes double quotes (e.g. as part of the argument), escape the double quotes by means of the backslashes, for example, -Dmy.prop=\"quoted_value\".
Pass environment variablesLocalTo pass specific variables to the server environment, select this check box and specify the variables:
  • To add a variable, click add and specify the variable name and value in the Name and Value fields respectively.
  • To remove a variable from the list, select the variable and click delete.
PortLocalUse this field to change the debugger port (if necessary).
Debugger SettingsLocalClick this button to edit the debugger options on the Debugger page of the Settings dialog.
TransportRemote Specify the "transport" settings for the connection with the debugger. In technical terms, these are the parameters for the -Xrunjdwp command-line option:
  • Socket. Specify the debugger port in the Port field. The combination of these two settings translates into
    -Xrunjdwp:transport=dt_socket,address=<port>,suspend=n,server=y
  • Shared memory. Specify the shared memory address in the corresponding field. The combination of these two settings translates into
    -Xrunjdwp:transport=dt_shmem,address=<address>,suspend=n,server=y

Note that as you change the transport settings, what follows transport= within -Xrunjdwp in the area above also changes. In this way you control the corresponding command-line debugger parameters which you cannot edit directly.

Before Launch options

ItemDescription
Before Launch Specify which activities should be performed before starting the run/debug configuration:
  • Make. If this check box is selected, the project is compiled automatically prior to running or debugging. This option helps you ensure that all changes are included and compiled.
  • Build Artifacts. If this check box is selected, the specified artifacts will be built prior to running or debugging. To define the artifacts to be built, click browseButton and select the desired artifacts.
  • Run Ant target. If this check box is selected, the specified Ant target will be built prior to running or debugging. To define the Ant target, click browseButton and select the desired target.

    To learn more about Ant support, refer to the Ant Support section.

  • Run Maven goal. If this check box is selected, the specified Maven goal will be executed prior to running or debugging. To define the Maven goal to be executed, click browseButton and select the desired goal.

    To learn more about Maven support, refer to the Maven Support section.

  • Show this page. Select this check box if you want the Run/Debug Configurations dialog to be shown every time you launch this run/debug configuration.

The Before Launch actions are performed in the order they appear in the Run/Debug Configurations dialog.

Toolbar

ItemDescription
add (Insert)Use this icon or shortcut to create a new run/debug configuration.
delete (Delete)Use this icon or shortcut to delete the selected run/debug configuration.
copy (Ctrl+D)Use this icon or shortcut to create a copy of the selected run/debug configuration.
settings Click this button to edit the default settings for run/debug configurations.
arrowUp arrowDownUse these buttons to move the selected run/debug configuration up and down in the list.

The order of configurations in the list defines the order in which the configurations appear in the corresponding list on the main toolbar.

See Also

Concepts:

Procedures:

Reference:

Web Resources: