Run/Debug Configuration: WebLogic Server

or Alt+Insert

Add an artifact or an external resource to the list.

or Alt+Delete

Remove the selected artifacts and external resources from the list.

or F4

Configure the selected artifact. The Artifacts page of the Project Structure dialog will open.

Deployment method

For local run configurations:

• Weblogic.Deployer: The server admin interface is used.

• Auto deploy: The artifact is copied to the server auto-deployment folder.

Check EJB CMP datasources

If this checkbox is selected, the names of persistent entities for EJB CMP data sources are validated. The validation is based on the mappings defined in EJB deployment descriptor files specific to WebLogic Server (for example, weblogic-ejb-jar.xml and weblogic-cmp-rdbms-jar.xml).

Install as a library

Install the selected artifact as a library. If enabled, selecting the deployment plan is not available.

Deployment plan

Specify the deployment plan that defines a valid configuration for the target environment. You can specify the deployment plan only for artifacts deployed as apps, not installed as libraries.

Is Active

Select checkboxes 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:

• Full paths to specific files.

• Ant patterns that define the range of files to be displayed.

• Aliases to substitute for full paths or patterns. These aliases are also displayed in the headers of the tabs where the corresponding log files are shown.

  If a log entry pattern defines more than one file, the tab header shows the name of the file instead of the log entry alias.

Skip Content

Select this checkbox to have the previous content of the selected log skipped.

Save console output to file

Select this checkbox 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 checkbox 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 checkbox 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.

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 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.

 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.

Use default:

• If this checkbox is selected, the default script is used.

   in this case opens the Default Startup Script dialog which shows the contents of the Startup script field (readonly).

• Clear this checkbox to change the parameters passed to the script or to specify a different script:

  • To specify the script, click and select the desired script in the dialog that opens.

  • To specify the parameters, click and specify the script parameters and VM options in the Configure VM and Program Parameters dialog.

    When specifying the parameters and options, follow these rules:

    • Use spaces to separate individual parameters and options, for example, -client -ea -Xmx1024m.

    • If a parameter or an option includes spaces, enclose the spaces or the argument that contains the spaces in double quotes, for example, some" "arg or "some arg".

    • If a parameter or an option includes double quotes (e.g. as part of the argument), escape the double quotes by means of the backslashes, for example, -Dmy.prop=\"quoted_value\".

Shutdown script

Specify the script to be used to stop the server.

Use default:

• If this checkbox is selected, the default script is used.

   in this case opens the Default Shutdown Script dialog which shows the contents of the Shutdown script field (readonly).

• Clear this checkbox to change the parameters passed to the script or to specify a different script:

  • To specify the script, click and select the desired script in the dialog that opens.

  • To specify the parameters, click and specify the script parameters and VM options in the Configure VM and Program Parameters dialog.

    When specifying the parameters and options, follow these rules:

    • Use spaces to separate individual parameters and options, for example, -client -ea -Xmx1024m.

    • If a parameter or an option includes spaces, enclose the spaces or the argument that contains the spaces in double quotes, for example, some" "arg or "some arg".

    • If a parameter or an option includes double quotes (e.g. as part of the argument), escape the double quotes by means of the backslashes, for example, -Dmy.prop=\"quoted_value\".

Pass environment variables

To pass specific variables to the server environment, select this checkbox and specify the variables:

• To add a variable, click and specify the variable name and value in the Name and Value fields respectively.

• To remove a variable from the list, select the variable and click .

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.

 Run /

 Debug

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...

Name

Specify a name for the run/debug configuration to quickly identify it when editing or running the configuration, for example, from the Run popup Alt+Shift+F10.

Allow parallel run

Select to allow running multiple instances of this run configuration in parallel.

By default, it is disabled, and when you start this configuration while another instance is still running, IntelliJ IDEA suggests to stop the running instance and start another one. This is helpful when a run/debug configuration consumes a lot of resources and there is no good reason to run multiple instances.

Store as project file

Save the file with the run configuration settings to share it with other team members. The default location is .idea/runConfigurations. However, if you do not want to share the .idea directory, you can save the configuration to any other directory within the project.

By default, it is disabled, and IntelliJ IDEA stores run configuration settings in .idea/workspace.xml.

Alt+Insert

Create a run/debug configuration.

Alt+Delete

Delete the selected run/debug configuration. Note that you cannot delete default configurations.

Ctrl+D

Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.

The button is displayed only when you select a temporary configuration. Click this button to save a temporary configuration as permanent.

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 or and buttons.

To remove grouping, select a folder and click .

Click this button to sort configurations in the alphabetical order.

Alt+Insert

Click this icon to add one of the following available tasks:

• Run External tool: select to run an external application. In the dialog that opens, select one or multiple applications you want to run. If it is not defined in IntelliJ IDEA yet, add its definition. For more information, see External tools and External Tools.

• Run Another Configuration: select to execute another run/debug configuration. In the dialog that opens, select the configuration to be run.

• Build: select to compile the specified module. The Build Module command will be executed.

  If an error occurs during compilation, IntelliJ IDEA won't attempt to start the run/debug configuration.

• Build Project: select to compile the entire project. The Build Project command will be executed.

  If an error occurs during compilation, IntelliJ IDEA won't attempt to start the run/debug configuration.

• Build, no error check: the same as the Build option, but IntelliJ IDEA will try to start the run/debug configuration irrespective of the compilation results.

• Build Artifacts: select this option to build an artifact or artifacts. In the dialog that opens, select the artifact or artifacts that should be built.

• Launch Web Browser: select this option to have a browser started. In the dialog that opens, select the type of the browser and provide the start URL. Also, specify if you want the browser be launched with JavaScript debugger.

• Run Ant target: select this option to run an Ant target. In the dialog that opens, select the target to be run.

• Run Grunt task: select this option to run a Grunt task.

  In the Grunt task dialog that opens, specify the Gruntfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Grunt tool.

  Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the grunt-cli package.

• Run gulp task: select this option to run a Gulp task.

  In the Gulp task dialog that opens, specify the Gulpfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Gulp tool.

  Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the gulp package.

• Run Maven Goal: select this option to run a Maven goal. In the dialog that opens, select the goal to be run.

• Run npm script: select this option to execute an npm script.

  In the NPM Script dialog that opens, specify the npm run/debug configuration settings.

• Compile TypeScript: select to run the built-in TypeScript compiler and thus make sure that all the changes you made to your TypeScript code are reflected in the generated JavaScript files. In the TypeScript Compile Settings dialog that opens, select or clear the Check errors checkbox to configure the behaviour of the compiler in case any errors are detected:

  • If the Check errors checkbox is selected, the compiler will show all the errors and the run configuration will not start.

  • If the Check errors checkbox is cleared, the compiler will show all the detected errors but the run configuration still will be launched.

• Generate CoffeeScript Source Maps: select this option to generate the source maps for your CoffeeScript sources. In the dialog that opens, specify where your CoffeeScript source files are located.

• Run Remote External Tool: adds a remote SSH external tool.

• Run Rake task: add a Rake task to be executed prior to running or debugging. To choose a Rake task, click the browse button , and select the desired task from the list of available tasks.

  Note that code completion is available here.

  

• Run JRuby compiler: choose this option to execute JRuby compiler with the specified target path, compiler process heap size, and command line parameters (if any).

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 checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.

Activate tool window

By default this checkbox is selected and the Run or the Debug tool window opens when you start the run/debug configuration.

Otherwise, if the checkbox is cleared, the tool window is hidden. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5.