Run/Debug Configuration: CloudBees Server
The Tomcat instance embedded in CloudBees is used as a server. This Tomcat instance is included in the server client libraries. You can download those libraries using a quick fix provided right in the run configuration:
- Name field and Share option
- Server tab
- Deployment tab
- Logs tab
- Code Coverage tab
- Before Launch options
Name field and Share option
|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.
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.
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.
|The field underneath After launch||
Specify the URL the browser should go to when started.
Most likely, the default |
|VM options||If necessary, specify the command-line options to be passed to the server JVM at the server start.
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).|
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.
|JRE||By default, the project JDK is used to run the application. If you want to specify an alternative JDK or JRE here, select it from the drop-down list.|
|HTTP port||The server HTTP port.|
|JNDI port||The server JNDI port.|
Specify an artifact or an external resource to be deployed on the server. (An external resource means a deployable Web component such as a WAR file which is not represented by a project artifact.)
There should be exactly one item in the deployment list. "Exploded" artifacts cannot be used.
To add an item to the list, click and do one of the following:
- To add an artifact, select Artifact and choose the desired artifact in the dialog that opens.
- To add an external resource, select External Source and choose the location of the desired resource in the dialog that opens.
(Alt+Delete) removes the selected items from the list.
|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.
Before Launch options
Specify which tasks should be carried out before starting the run/debug configuration.
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.