Name field
| Item | Description |
|---|---|
| Name | Use this field to edit the name of the run/debug configuration. |
Server Tab
| Item | Description |
|---|---|
| Application Server | Select the server configuration to be used.
Click Configure to create a new server configuration or edit an existing one. (The Application Servers dialog will open.) |
| Start browser | Select this check box to run the default Web browser to study your application output there. |
| With JavaScript Debugger | If this check box is selected, the Web browser is started with the JavaScript debugger enabled.
Note 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 page | In 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 options | If 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 When specifying the options, follow these rules:
|
| Perform on 'Update' action |
Select the necessary option for the Update application action.
|
| Show dialog |
Select this check box if you want to see the Update <application name> dialog every time you perform
the Update application action.
The Update <application name> dialog is used to view and change the current update option prior to actually updating the application. |
| On frame deactivation |
Specify which application update actions should be performed when switching from IntelliJ IDEA to a different application
(for example, a Web browser).
(Frame deactivation means switching to a different application.)
If no update actions are required, select Do nothing. Otherwise, select the necessary update option. Note that the Restart server option is not available. |
| Web Artifact to deploy | Select the artifact to be deployed on the server. |
| Port | Specify the server HTTP port. |
| Server parameters | If necessary, specify the command-line arguments to be passed to the server. |
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.
| Item | Description |
|---|---|
| Is Active | Select this check box to have the selected log file displayed. |
| Log File Entry | This read-only field lists the log files to show. The list can contain:
|
| Skip Content | Select this check box to have the previous content of the selected log skipped. |
| Add | Click this button to add another log file entry. Specify the associated properties in the Edit Log Files Aliases dialog. |
| Edit | Click this button to edit the properties of the selected log file entry in the Edit Log Files Aliases dialog. |
| Remove | Click this button to remove the selected log entry from the list. |
| Save console output to file | Select this check box to save the console output in a specified file.
In the field underneath the check box, specify the absolute path to the file.
Alternatively, use |
Code Coverage tab
Use this tab to configure code coverage monitoring options.
Note that this tab is not available for remote servers.
| Item | Description |
|---|---|
| Choose code coverage runner | Select the desired code coverage runner. |
| Sampling | Select this option to measure code coverage with minimal slow-down. |
| Tracing | Select this option to collect accurate branch coverage. This mode is available for the IntelliJ IDEA code coverage runner only. |
| Track per test coverage | Select this check box to detect lines covered by one test and all tests covering line. |
| Packages and classes to record code coverage data | If 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 Remove. |
| Enable coverage in test folders. | Select this check box to include the test source folders in code coverage analysis. |
Before Launch and Share configuration options
| Item | Description |
|---|---|
| Before Launch |
Specify which activities should be performed before starting the run/debug configuration:
Note The Before Launch actions are performed in the order they appear in the Run/Debug Configurations dialog. Thus, the artifacts are built before running the Ant targets, etc. |
| Share configuration |
If this check box is selected, the run/debug configuration is available to other team members.
|
Toolbar
| Item | Description |
|---|---|
(InsertInsert)
|
Use this icon or shortcut to create a new run/debug configuration. |
(DeleteDelete)
|
Use this icon or shortcut to delete the selected run/debug configuration. |
(Ctrl+DCommand D)
|
Use this icon or shortcut to create a copy of the selected run/debug configuration. |
![]() |
Click this button to edit the default settings for run/debug configurations. |
![]() |
Use 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. |

.
next to the field to
open the
(
(
(
(
