How To: Use Tomcat in Intellij IDEA Community
Recently I started working on a project that required me to have the backend part installed locally, instead of using a remote backend. The project uses Maven as a build tool and it deploys the code to a Tomcat server.
I got cracking and started configuring the project on my local machine. The first thing I noticed is that Intellij IDEA Community does not have a Tomcat plugin, unlike the Ultimate edition, that has one out of the box.
Many Google searches later I found a few plugins that might do the trick but when I tried using them, the famous NullPointerException happened and I started looking for an alternative. I found some inspiration on Github, but not in the form I wanted, but it was good enough to get me started.
Bellow is a short tutorial on how to setup Tomcat in Intellij IDEA Community to run/debug, and how to use Maven to build your project and then deploy it to Tomcat.
Prerequisites
- Install Intellij IDEA Community.
- Install Tomcat — For my project I’ve used Tomcat 8. You can get it from here.
- Install Maven.
Tomcat Configuration
Make sure you install Tomcat in a place that doesn’t require admin access, for example next to your project.
After that, open File -> Settings and expand Tools and select External Tools .
You can add a new tool with whatever name you want. I named mine, Tomcat. For tool settings, select the catalina.bat file, usually located in the bin folder of your Tomcat installation. For example mine is C:\apache-tomcat-8.5.34\bin\catalina.bat . And last but not least set an argument with the command jpda run . The working directory should be set automatically.
Tomcat External Tool
Start Tomcat
If you go to Tools -> External Tools and click on Tomcat, it should start the Tomcat server.
Maven build and deploy to Tomcat
Now that you’re done with the Tomcat configuration you want the ability to build using Maven and deploy to the now working Tomcat server.
To achieve this you’ll need to head over to Run -> Edit Configurations , click the «+» and select Maven . Don’t forget to name your new configuration. Select your project location and add the following command line.
Exit fullscreen mode
What this line does is that it builds the project, using Maven, and then gets the file from the specified path (that’s usually configured in your project) and copies it to the webapps folder in Tomcat. Tomcat then knows it has a new version of the file and redeploys it.
Build and deploy to Tomcat
Tomcat Remote Debug
Like all applications you want the ability to debug your backend. To achieve this you’ll need to add a new configuration like the previous step. The only difference this time is that when you click «+» you’ll need to select Remote .
Give your configuration a name. You’ll need to set the Debugger mode to Attach to remote JVM , the Transport to Socket , the Host to localhost and lastly the Port to 8000 . That way when you start the configuration, Intellij will connect via Socket to the Tomcat server that emits via port 8000 . You can change the port for Tomcat, to something else, in the Tomcat server.xml file, in the config folder.
Tomcat Remote Debug
Once the Tomcat server is started you can run this configuration. Just click on Run -> Debug and then select the newly created configuration.
If you want to keep a record of all the logs when debugging, you can achieve this by going to the Logs tabs in the newly created Remote configuration and set the Save console output to file to the logs folder of your Tomcat installation. In my case it was C:\apache-tomcat-8.5.34\logs*.* .
Tomcat Remote Debug Logs
That is it. @ me on Twitter if you think I’ve missed something or if there is another way of doing this without installing Eclipse or purchasing the Ultimate edition of Intellij IDEA.
Русские Блоги
Руководство по настройке Tomcat IDEA Community Edition
Я видел много сообщений в блогах, в которых рассказывалось о tomcat с использованием maven. Я не пробовал этот метод, но в версии сообщества действительно есть tomcat -> Smart Tomcat.
Откройте настройку IDEA, Crtl + Alt + S или File-> в плагинах в настройках, найдите tomcat, чтобы увидеть его, нажмите «Установить», чтобы установить его. 
После завершения установки перезапустите инструмент IDEA, затем щелкните "Добавить конфигурации" в правом верхнем углу IDEA, щелкните "Шаблоны", чтобы увидеть Smart Tomcat, а затем щелкните "Конфигурация", чтобы настроить tomcat. 
На этом этапе при добавлении кота впервые появилось нулевое значение, и добавление было неудачным. 
Моя проблема в том, что мне нравится устанавливать программное обеспечение в Program Files, а мой Tomcat находится в D: \ Program Files, возможно, в пути есть пробел, поэтому конфигурация была Нулевое значение, этот путь подходит для затмения.
Итак, я скопировал tomcat в корневой каталог диска D, и он был успешно добавлен.
Имя: название проекта.
Tomcat: путь к Tomcat
Развертывание: путь к веб-приложениям
Контекстный путь: контекстный путь, он будет автоматически идентифицирован, как правило, нет необходимости изменять
Порт сервера: порт прослушивания сервера 8080 (обычно изменяется самостоятельно)
Параметры виртуальной машины: настройки параметров виртуальной машины Java (необязательно)
После завершения настройки нажмите треугольную кнопку запуска в правом верхнем углу, чтобы запустить Tomcat в обычном режиме. 
Интеллектуальная рекомендация
Компонент шагов ANTD+Vue добавляет пользовательский контент в стиле к панели шагов (ниже)
Если значок, указанный в компоненте Steps в ANTD, не может соответствовать нашим требованиям, вам необходимо использовать пользовательскую картинку для его реализации. Например, реализован следующий п.
Метод Java тяжелая нагрузка и механизм передачи значений
Метод перегрузка концепция: В одном и том же классе разрешен тот же метод имени, до тех пор, пока их параметры или типы параметров различны. Особенности тяжелой нагрузки: Два из одинаковых различий: о.
Разработчик общий сайт
http://www.hollischuang.com/archives/1459?hmsr=toutiao.io&utm_medium=toutiao.io&utm_source=toutiao.io В качестве разработчика Java вы часто должны иметь дело с широким спектром инструме.
P4 коммутатор сетевой эксперимент
В настоящее время в моей лаборатории есть коммутатор Edge-core P4, модель которогоWedge 100BF-32XКоммутатор имеет в общей сложности 32 порта 100G, но он может обмениваться данными с сервером 40G через.
Run/Debug Configuration: Tomcat Server
Tomcat Server run/debug configurations let you deploy and debug your applications on Apache Tomcat. The Tomcat and TomEE Integration plugin must be enabled.
Server tab for a local configuration
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.)
Select this checkbox 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 checkbox 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.
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:
Use spaces to separate individual options, for example, -client -ea -Xmx1024m .
If an option includes spaces, enclose the spaces or the argument that contains spaces in double quotes, for example, some" "arg or "some arg" .
If an option includes double quotes (as part of the argument), escape the double quotes using backslashes, for example, -Dmy.prop=\"quoted_value\" .
You can pass environment variable values to custom Java properties. For example, if you define a variable MY_ENV_VAR , you can pass it to the foo property as follows:
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:
Update resources. All changed resources are updated (HTML, JSP, JavaScript, CSS and image files).
Update classes and resources. Changed resources are updated; changed Java classes (EJBs, servlets, etc.) are recompiled.
In the debug mode, the updated classes are hot-swapped. In the run mode, IntelliJ IDEA just updates the changed classes in the output folder. Whether such classes are actually reloaded in the running application, depends on the capabilities of the runtime being used.
Redeploy. The application artifact is rebuilt and redeployed.
Restart server. The server is restarted. The application artifact is rebuilt and redeployed.
For packed artifacts, the available options are:
Hot swap classes. Changed classes are recompiled and reloaded at runtime. This option works only in the debug mode.
Redeploy. The application artifact is rebuilt and redeployed.
Restart server. The server is restarted. The application artifact is rebuilt and redeployed.
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.
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.
The server HTTP port.
The server HTTPS port.
The server JMX port.
The server AJP port.
Deploy applications configured in Tomcat instance
The Tomcat configuration files, among other things, may list the applications that should be deployed at the server start. If this checkbox is selected, all the applications so listed will be deployed on the server in addition to the artifacts specified on the Deployment tab.
If the checkbox is not selected, only the artifacts and the external resources specified on the Deployment tab will be deployed.
Preserve sessions across restarts
Select this checkbox to preserve active HTTP sessions when restarting the server.
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.
With JavaScript debugger
If this checkbox 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.
On ‘Update’ action
Select the necessary option for the Update application function ( or Ctrl+F10 in the Run or Debug tool window).
The options are:
Hot swap classes. Changed classes are recompiled and reloaded at runtime. This option works only in the debug mode.
Redeploy. The application artifact is rebuilt and redeployed.
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.
The server JMX port.
If you are not deploying anything with this run configuration, you don’t need to specify this port.
This section contains the settings related to staging. An example of remote staging settings for a mounted folder is provided after this table.
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:
Same file system. Select this option if the target server is installed on your local computer. The artifacts in this case are deployed locally and, thus, don’t need to be transferred to a remote host.
Local or mounted folder. The staging environment is a local folder or is accessed as a mounted folder.
If the list is empty, you have to enable the FTP/SFTP Connectivity 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.
Click to the right of the list.
In the Add Server dialog, specify the configuration name, select the type, and click OK .
On the Connection tab, specify the settings in the Upload/download project files section.
The rest of the settings don’t matter.
Click OK in the Deployment dialog.
When deploying to the remote host, the application artifact or artifacts are placed into a staging folder which should be accessible to Tomcat. The settings in this section define the location of this staging folder.
Note that if Same file system is selected for Type and Host , no settings in this section need to be specified.
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.
Remote connection settings
The settings for accessing deployed applications.
The fully qualified domain name or the IP address of the Tomcat host.
The server HTTP port.
An example of remote staging settings for a mounted folder
C:\shared is a shared folder on the remote host, which is mounted to the local computer as the drive X: .
The folder that you are going to use for staging is C:\shared\staging .
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: staging
Staging/Mapped as: C:\shared\staging
Deployment tab
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.
Note that deployment to a remote server is supported only for Tomcat 5 or later versions. Also note that to be able to deploy applications to a remote Tomcat server, enable JMX support on the server. To do that, pass the following VM options to the server Java process:
<host> is the server hostname (domain name) or IP address.
If catalina.bat or catalina.sh is used to start the server, these options may be passed to the server using the CATALINA_OPTS environment variable.
Add an artifact or an external resource to the list.
Remove the selected artifacts and external resources from the list.
Configure the selected artifact. The Artifacts page of the Project Structure dialog will open.
Specify the context root for an artifact or external resource: select the artifact or the resource and type or select the context root.
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.
Select checkboxes in this column to have the log entries displayed in the corresponding tabs in the Run tool window or Debug tool window.
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.
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.
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.
Startup/Connection tab for a local configuration
Use to switch between the settings for the run, debug and code coverage modes.
Specify the script to be used to start the server.
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\" .
Specify the script to be used to stop the server.
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 .
Use this field to change the debugger port.
Click this button to edit the debugger options on the Debugger page of the Settings dialog.
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.
Common settings
When you edit a run configuration (but not a run configuration template), you can specify the following options:
Specify a name for the run configuration to quickly identify it among others when editing or running.
Allow parallel run
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 stopping the running instance and starting another one. This is helpful when a run 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 .
Toolbar
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.
Tomcat in Intellij Idea Community Edition
Is it possible to run a web application using Tomcat Server in Intellij Idea Community Edition?
I tried to find some information about it but haven’t achived any success.
17 Answers 17
Intellij Community does not offer Java application server integration. Your alternatives are
- buying Intellij licence,
- switching to Eclipse 😉
- installing Smart Tomcat plugin https://plugins.jetbrains.com/plugin/9492, make following settings (image)
- installing IDEA Jetty Runner plugin https://plugins.jetbrains.com/plugin/7505
- running the application server from Maven, Gradle, whatever, as outlined in the other answers.
I personally installed the Jetty Runner plugin (Jetty is fine for me, I do not need Tomcat) and I am satisfied with this solution. I had to deal with IntelliJ idea — Jetty, report an exception, though.
If you are using maven, you can use this command mvn tomcat:run , but first you add in your pom.xml this structure into build tag, just like this:
Using Maven, try tomcat7-maven-plugin :
Run it using tomcat7:run-war
Tomcat (Headless) can be integrated with IntelliJ Idea — Community edition.
Step-by-step instructions are as below:
Add tomcatX-maven-plugin to pom.xml
Add new run configuration as below:
Invoke Tomcat in Run/Debug mode directly from IntelliJ Run >> Run/Debug menu
NOTE: Though this is considered a hacking of using using Tomcat integration features of IntelliJ — Enterprise version features, but I would consider this a programmatic way integrating tomcat to the IntelliJ Idea — community edition.
Yes, you can use maven plugin, or simple java program. No need for IDE plugin. See for example Main class from https://devcenter.heroku.com/articles/create-a-java-web-application-using-embedded-tomcat
Tomcat can also be integrated with IntelliJ Idea — Community Edition with Tomcat Runner Plugin.
The maven plugin and embedded Tomcat are usable work-arounds (I like second better because you can debug) but actual web server integration is a feature only available in intelij paid editions.
Yes, its possible and its fairly easy.
- Near the run button, from the dropdown, choose «edit configurations. «
- On the left, click the plus, then maven and rename it «Tomcat» on the right side.
- for command line, enter «spring-boot:run»
- Under the runner tab, for ‘VM Options’, enter «-XX:MaxPermSize=256m -Xms128m -Xmx512m -Djava.awt.headless=true» NOTE: ‘use project settings’ should be unticked.
- For environment variables enter «env=dev»
- Finally, click Ok.
When you’re ready to press run, if you go to «localhost:8080/< page_name > » you’ll see your page.
My pom.xml file is the same as the Official spring tutorial Serving Web Content with Spring MVC
Well the question is already answered, however what I am writing here is just my observation so other fellows in the community can save some of their time. I tried running a spring-mvc project using the embedded tom-cat in Intellij communit edition.
First try I did was using the Gradle tom-cat plugin, however the problem that I faced there is the tomcat server just starts once, after that from the second start the build complains saying that a container is already running. There are so many open thread on the web about this, for some it works and for most of the people (almost 90% of the web threads that I broke my head with, faced the same problem of container not getting started the second time. The resolution is not there.
After wasting a lot lot of my time, I finally decided to switch to maven tom-cat plugin and do the same spring-mvc setup with maven that I did with gradle and VOILA! it worked in the first short.
So long story short, if you are setting up spring-mvc project in intellij community edition, please consider maven tomcat plugin.
Hope this helps somebody’s hours of exploration across various web forums.