Run/Debug Configuration: Spring DM Server (Remote)
Note that if you are starting the server by means of the default script
startup.sh, you should properly set the environment variable
- Server tab for a remote configuration
- Deployment tab
- Logs tab
- Startup/Connection tab for a remote configuration
- Common options
- Before Launch options
See also, Working with Server Run/Debug Configurations.
Server tab for a remote configuration
| Select the server configuration to be used. Note that this is a local server configuration. (When working with a remote server, the same server version must be available locally.) |
Click Configure to create a new server configuration or edit an existing one. (The Application Servers dialog will open.)
| Select this checkbox to start a web browser after connecting to the server and deploying the artifacts. |
Select the browser from the list. Click (Shift+Enter) to configure your web browsers.
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.
On 'Update' action
| Select the necessary option for the Update application function ( or N/A in the Run or Debug tool window). |
The options are:
| Select this checkbox 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.
Specify the JMX server port.
Click this button to ping the JMX port on the server.
Specify the name of the user on whose behalf IntelliJ IDEA will connect to the JMX server port.
Specify the password of the JMX user.
| Select the way the staging environment or host is accessed for transferring the application artifact or artifacts from your local computer. (In the user interface of IntelliJ IDEA this setting is also referred to as the connection type.) |
The available options are:
If the list is empty, you have to enable the Remote Hosts Access plugin which supports the corresponding functionality.
|If Same file system is selected for Type, the only available option for Host is also Same file system. |
In all other cases, the list contains the existing configurations of the selected type. So each configuration corresponds to an individual (S)FTP connection, or a local or mounted folder.
Select an existing configuration or create a new one.
To create a new configuration:
When deploying to the remote host, the application artifact or artifacts are placed into a staging folder (deployment target folder). This folder should be accessible to the server. The settings in this section define the location of this staging folder.
Path from root
|The path to the staging folder relative to the local or mounted folder, or the root of the (S)FTP host. |
You can use to select the folder in the Choose target path dialog.
| The absolute path to the staging folder in the local file system of the remote host. |
The path should be specified as a URL, e.g.
When deploying to the remote host, the plans (artifacts) are placed into a watched repository. The settings in this section describe this repository.
Path from root
|The path to the repository folder relative to the local or mounted folder, or the root of the (S)FTP host. |
You can use to select the folder in the Choose target path dialog.
Specify the name of the watched repository the way it is defined in the configuration of the remote server.
Remote connection settings
The settings for accessing deployed applications.
The fully qualified domain name or the IP address of the server host.
The server HTTP port.
An example of remote staging settings for a mounted folder
C:\sharedis a shared folder on the remote host which is mounted to the local computer as the drive
The folder that you are going to use for staging is
Here are the corresponding remote staging settings:
Type: Local or mounted folder.
Host: The configuration should be selected in which the value in the Folder field is
X:\(the Upload/download project files section on the Connection tab of the Deployment dialog).
Staging/Path from root:
Use this tab to specify which artifacts 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), click the Add button (). To edit the settings for an artifact or external resource, select the corresponding item in the list and use the controls below.
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.
Startup/Connection tab for a remote configuration
This tab shows command-line options for starting the server JVM in the run and debug modes.
Use to switch between the settings for the run and debug modes. The settings are shown in the area under To run/debug...
To run/debug remote server JVM...
The command-line options for starting the server JVM. These are shown just for copying elsewhere.
Transport (and all that follows)
The GUI for generating the remote debug command-line options shown in the area under To run/debug...
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.
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.