Run/Debug Configuration: Spring DM Server (Local)
This feature is supported in the Ultimate edition only.
Run | Edit Configurations | | Spring dmServer | Local
Spring dmServer run/debug configurations let you deploy and debug your applications on SpringSource dm Server and Virgo. (The dmServer Support plugin must be enabled.)
Note that if you are starting the server by means of the default script startup.bat
or startup.sh
, you should properly set the environment variable JAVA_HOME
.
- Name field and Share option
- Server tab for a local configuration
- Deployment tab
- Logs tab
- Code Coverage tab
- Startup/Connection tab for a local configuration
- Before Launch options
- Toolbar
See also, Working with Server Run/Debug Configurations.
Name field and Share option
Item | Description |
---|---|
Name | Use this field to edit the name of the run/debug configuration. This field is not available when editing the run/debug configuration defaults. |
Share | Select this check box 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 This check box is not available when editing the run/debug configuration defaults. |
Server tab for a local configuration
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.) If the message Error: JMX arguments are incompatible with IDEA is shown in the lower part of the dialog, click Fix. As a result, the necessary changes are made to the script |
After launch | Select this check box to start a web browser after starting the server and deploying the artifacts. Select the browser from the list. Click (Shift+Enter) to configure your web browsers. |
With JavaScript debugger | If this check box is selected, the web browser is started with the JavaScript debugger enabled. Note that JavaScript debugging is available only for Firefox and Google Chrome. When you debug your JavaScript in Firefox for the first time, the JetBrains Firefox extension is installed. |
The field underneath After launch | Specify the URL the browser should go to when started. In most typical cases, this URL corresponds 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 next to the field to open the VM Options dialog where the text entry area is larger. When specifying the options, follow these rules:
|
On 'Update' action | Select the necessary option for the Update application function ( or Ctrl+F10 in the Run or Debug tool window). The update options are different for exploded and packed artifacts. For exploded artifacts, the available options are:
For packed artifacts, the available options are: |
Show dialog | Select this check box if you want to see the Update dialog every time you use the Update application function. The Update dialog is used to select the update option prior to actually updating the application. |
On frame deactivation | Specify what IntelliJ IDEA should do when you switch from the IDE to a different application (for example, a web browser). (Frame deactivation means switching to a different application.) The options other than Do nothing have the same meanings as in the case of the Update action. |
Port | Specify the HTTP server port. |
JMX Port | Specify the JMX server port. |
JMX User | Specify the name of the user on whose behalf IntelliJ IDEA will connect to the JMX server port. |
JMX Password | Specify the password of the JMX user. |
Local staging / Repository target | Select the watched repository to place your plans (artifacts) to. |
Deployment tab
Use this tab to specify which artifacts and/or external resources should be deployed onto the server. (An external resource means a deployable Web component such as a .war
file which is not represented by a project artifact. Usually, such components are stored outside of the project scope.)
To add items to the deployment list (shown under Deploy at the server startup), use . To edit the settings for an artifact or external resource, select the corresponding item in the list and use the controls in the right-hand part of the tab. For more information, see the table below.
Item | Description |
---|---|
or Alt+Insert | Use this icon or shortcut to add an artifact or an external resource to the list.
|
or Alt+Delete | Use this icon or shortcut to remove the selected artifacts and external resources from the list. |
or F4 | Use this icon or shortcut to configure the selected artifact. (The Artifacts page of the Project Structure dialog will open.) |
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 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 Entry | The read-only fields in this column list 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. |
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. | |
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.
Startup/Connection tab for a local configuration
Item | Description |
---|---|
Run / Debug / Coverage | Use to switch between the settings for the run, debug and code coverage modes. |
Startup script | Specify the script to be used to start the server.
|
Shutdown script | Specify the script to be used to stop the server.
|
Pass environment variables | To pass specific variables to the server environment, select this check box and specify the variables: |
Port | Use this field to change the debugger port. |
Debugger Settings | Click this button to edit the debugger options on the Debugger page of the Settings dialog. |
Before Launch options
Specify which tasks should be carried out before starting the run/debug configuration.
Item | Shortcut | Description |
---|---|---|
Alt+Insert | Click this icon to add a task to the list. Select the task to be added, for example:
| |
Alt+Delete | Click this icon to remove the selected task from the list. | |
Enter | Click this icon to edit the selected task. Make the necessary changes in the dialog that opens. | |
Alt+Up/Alt+Down | 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 check box to show the run/debug configuration settings prior to actually starting the run/debug configuration. | |
Activate tool window | If this check box is selected, the Run or the Debug tool window opens when you start the run/debug configuration. Otherwise, the tool window isn't shown. However, when the configuration is running, you can open the corresponding tool window for it yourself if necessary. |
Toolbar
Item | Shortcut | Description |
---|---|---|
Alt+Insert | Create a run/debug configuration. | |
Alt+Delete | Delete the selected run/debug configuration. | |
Ctrl+D | Create a copy of the selected run/debug configuration. | |
View and edit the default settings for the selected run/debug configuration. | ||
Alt+Up/Alt+Down | 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. | |
You can group run/debug configurations by placing them into folders. To create a folder, select the configurations to be grouped and click . Specify the name of the folder. Then, to move a configuration into a folder, between the folders or out of a folder, use and . You can also drag a configuration into a folder. To remove grouping, select a folder and click . See also, Creating Folders and Grouping Run/Debug Configurations. |