Run/Debug Configuration: JSR45 Compatible Server
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:
The server you are going to work with supports JSR-45.
IntelliJ IDEA doesn't provide a dedicated plugin for integration with this server.
On this page:
| 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.)
Select this checkbox to run the default Web browser to study your application output there.
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.
|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 next to the field to open the VM Options dialog where the text entry area is larger.
When specifying JVM options, follow these rules:
On 'Update' action
| Select this checkbox 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.
Specify the Java package prefix to be used for jsp-to-servlet translation.
VM options variable
If 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.
Specify the HTTP server port.
Use JSP's line mapping model specific for WebSphere 5.1
|If the run/debug configuration is intended for working with WebSphere Server 5.1, select this checkbox 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.)
The DNS name or the IP address of the server host (for example,
Log File Entry
The read-only fields in this column list the log files to show. The list can contain:
Select this check box to have the previous content of the selected log skipped.
Save console output to file
Select 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 a message is printed to standard output stream
Select this check box to activate the output console and bring it forward if an associated process writes to Standard.out.
Show console when a message is printed to standard error stream
Select this check box to activate the output console and bring it forward if an associated process writes to Standard.err.
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.
Click this button to edit the properties of the selected log file entry in the Edit Log Files Aliases dialog.
Click this button to remove the selected log entry from the list.
Code Coverage tab
Use this tab to configure code coverage monitoring options.
Note that this tab is not available for remote servers.
Choose code coverage runner
Select the desired code coverage runner.
Select this option to measure code coverage with minimal slow-down.
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 checkbox 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 or to add classes or packages to the list.
To remove the classes or packages from the list, select the corresponding list items and click .
Enable coverage in test folders.
Select this checkbox to include the test source folders in code coverage analysis.
Select Run or Debug to show settings either for the run or the debug mode.
Run with Coverage
Select Run with Coverage to show settings for run with coverage mode.
| 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:
| 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:
Pass environment variables
|To pass specific variables to the server environment, select this checkbox and specify the variables: |
Use this field to change the debugger port (if necessary).
| Specify the "transport" settings for the connection with the debugger. In technical terms, these are the parameters for the |
Note that as you change the transport settings, what follows
When you edit a run configuration (but not a run configuration template), you can specify the following options for it:
In this text box, specify the name for the run/debug configuration. The name will help you identify the created configuration when you choose to edit it later, or when you invoke it, for example, from the Run popup (Shift+Alt+F10).
Select this checkbox to make the run/debug configuration available to other team members.
If the directory-based project format is used, the settings for a run/debug configuration are stored in a separate .xml file in the
If the file-based format is used, the settings are stored in the
Allow running in parallel
When disabled, every time a new run/debug configuration is launched, IntelliJ IDEA checks the presence of the other instances of the same run/debug configuration, and displays a confirmation dialog box. If you click OK in the confirmation dialog box, the first instance of the runner will be stopped, and the next one will take its place.
This makes sense when the usage of certain resources can cause conflicts, or when launching two run/debug configurations of the same type consumes too much of the CPU and memory resources.
If this checkbox is selected, it is possible to launch as many instances of the run/debug configuration as required. So doing, each runner will start in its own tab of the Run Tool Window or Debug Tool Window.
The tree view of run/debug configurations has a toolbar that helps you manage configurations available in your project as well as adjust default configurations templates.
Create a run/debug configuration.
Delete the selected run/debug configuration. Note that you cannot delete default configurations.
Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.
View and edit the default template for the selected run/debug configuration. The templates are used for newly created configurations.
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 when you choose a run/debug configuration.
Default templates of run/debug configurations are always sorted alphabetically.
Move into new folder / Create new folder
You can group run/debug configurations by placing them into folders.
To create a folder, select the configurations within a category, click , and specify the folder name. If only a category is in focus, an empty folder is created.
Then, to move a configuration into a folder, between the folders or out of a folder, use drag-and-drop or and buttons.
To remove grouping, select a folder and click .
Click this button to sort configurations in the alphabetical order.
Under the Templates node in the tree view of run configurations, you can select a run configuration template and edit its default settings. This will not affect the configurations that are already created, but will be used as defaults when creating new configurations of the corresponding type.
When you select the Templates node itself, you will be able to adjust general settings that apply to all run/debug configurations:
Configurations available in Run Dashboard
In this section you can create a list of run configurations available in the Run Dashboard — a tool window that helps you execute and manage multiple run/debug configurations.
Note that the dashboard will only display the configuration types for which you have created one ore more configurations.
Thus, if you add a configuration type for which no configurations exist in the project, this type will not be displayed on the dashboard until you create a configuration of this type.
Confirm rerun with process termination
|The behavior of this checkbox depends on whether the Single instance only option is selected for a particular run/debug configuration. |
Temporary configurations limit
Specify the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list.
Before Launch options
In this area you can specify tasks that must be be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.
Click this icon to add one of the following available tasks:
Click this icon to remove the selected task from the list.
Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.
Click these icons to move the selected task one line up or down in the list. (The tasks are performed in the order that they appear in the list.)
Show this page
Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.
Activate tool window
Otherwise, the tool window isn't shown. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5.