Intellij IDEA деплой на Tomcat
Хочу показать как можно быстро тестировать проект прям с IDE Intellij IDEA, а также расскажу плюсы от этого.
Шаг 0. Для чего это нужно?
Думаю вы уже работали над разработкой Java EE проектов ивам приходилось проверять его после написания очередной фитчи, а даже если не приходилось то придётся 🙂
Deploy – процесс развертывания (распаковки) проекта на сервере приложений.
О серверах приложений можно почитать тут. Так вот стандартный процесс деплоя:
1. Вы либо в ручную через Admin Panel или же через Console деплоите;
2. Вы используете Maven, Ant либо Gradle инструмент для этого.
Но не первый не второй способ не совсем удобный если вам к примеру нужно провести Debug проекта и отловить неисправность. И это одна из значительных причин использовать способ о котором я расскажу ниже.
Давайте теперь познакомимся собственно со способом деплоя используя Intellij IDEA.
Шаг 1. Готовим проект
Для того чтобы продемонстрировать данный способ мне необходимо иметь пример проекта для деплоя. Я буду использовать проект с этого урока Spring 3. JavaConfig на примере Spring MVC.
В скачанном вами проекте для деалоя на Tomcat необходимо в pom.xml добавить еще одну зависимость:
Открываем проект, справа в меню Maven Project выбираем clean | install как показано на изображении ниже, таким образом мы соберем наш проект и в итоге у нас получится war файл, который мы будем деплоить на сервер:
После этого в корне проекта появится папка target и в ней будет лежать ваш war архив.
Дальше нам нужно скачать сервер приложений Tomcat 8+ Скачать
Внимание! Вы можете использовать любой сервер приложения не обязательно Tomcat. Я рекомендую использовать его так как он лёгкий и быстро стартует.
Шаг 2. Конфигурируем Intellij IDEA для Deploy
Теперь в открытом вами проекте который вы хотите задеплоить, со студии IDEA выполните действия, которые показанные на изображении ниже:
После этого в появившемся окне нажмите на плюс и выберите Tomcat Server – Local:
После этого вводим имя и нажимаем Configure выбираете где лежит скачанный и распакованный Tomcat и жмете ОК.
Теперь переходите во вкладку Deployment жмем плюсик выбираем Artifact:
B в появившемся окне выбираете свой Artifact war:
Жмете ОК дважды. Вот общая конфигурация, которая должна появится у вас:
Шаг 3. Run и Debug
После настройки вы можите либо просто запускать ваш проект со студии либо проводить Debug со студии в зависимости от режима:
Зеленый треугольник просто запускает проект, а точней деплоит его и запускает в выбранном вами браузере при конфигурации.
Зеленый жучек деплоит проект на сервер и запускает Debug режим, который позволит вам отловить ошибки.
После запуска я получу задеплоиный проект:
Зеленый индикатор в Deployment говорит о том что проект удачно развернулся на сервере.
Tomcat in Intellij > Ask Question
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.
15 Answers 15
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:
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
- 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.
Using Maven, try tomcat7-maven-plugin :
Run it using tomcat7:run-war
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.
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, 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 s
- Finally, click Ok.
When you’re ready to press run, if you go to «localhost:8080/ » you’ll see your page.
My pom.xml file is the same as the Official spring tutorial Serving Web Content with Spring MVC
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.
You can use tomcat plugin with gradle. For more information, you here.
I used Jay Lin’s answer. Highly recommend it.
If you never used Maven before and don’t want to go deep into it: follow Jay Lin’s answer, but also do this:
right click on your project name -> Add Framework support -> Maven.
Then install maven from here http://maven.apache.org/install.html. Do what it says, run the commands.
Then install spring-boot from here https://mvnrepository.com.
Then follow the error messages if there are any — maybe you would need to install some other stuff (just google it and that mvnrepository.com would come up). To install use this command:
mvn install:install-file -Dgroup >
replace path with where you downloaded the jar file, replace version, group and artifact id with info from mvnrepository.com.
- Further errors I encountered:
I had to create a class in src/main/java (with simple System.out.println command in main) and add main.java.Hello in
tag in pom.xml . Btw, the pom.xml should appear itself when you do the first action from my answer — copy paste Jay Lin’s code there.
Another error I got was connected to JAVA_HOME variable and the verion stuff. Somewhy it thought jdk is 7th version and I was telling it was 8th. So I changed the java version tag in
Run/Debug Configuration: Tomcat Server
Run | Edit Configurations | </p><p><td >Select this checkbox to start a web browser after starting the server and deploying the artifacts.</p><p style=)
, escape the double quotes using backslashes, for example, -Dmy.prop=\»quoted_value\» .</p><p>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:</p><p style=)
.</p><p>The update options are different for exploded and packed artifacts.</p><p>For exploded artifacts, the available options are:</p><p>Update resources. All changed resources are updated (HTML, JSP, JavaScript, CSS and image files).</p><p> Update classes and resources. Changed resources are updated; changed Java > 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.</p><p>Redeploy. The application artifact is rebuilt and redeployed.</p><p>Restart server. The server is restarted. The application artifact is rebuilt and redeployed.</p><p>For packed artifacts, the available options are:</p><p>Hot swap classes. Changed classes are recompiled and reloaded at runtime. This option works only in the debug mode.</p><p>Redeploy. The application artifact is rebuilt and redeployed.</p><p>Restart server. The server is restarted. The application artifact is rebuilt and redeployed.</p><p><td >Select this checkbox if you want to see the Update dialog every time you use the Update application function.</p><p>The Update dialog is used to select the Update option prior to actually updating the application.</p><p><td >Specify what IntelliJ > The options other than Do nothing have the same meanings as in the case of the Update action.</p><p>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.</p><p>Deploy applications configured in Tomcat instance</p><p><td >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.</p><p>If the checkbox is not selected, only the artifacts and the external resources specified on the Deployment tab will be deployed.</p><p>Preserve sessions across restarts</p><p>Select this checkbox to preserve active HTTP sessions when restarting the server.</p><h2>Server tab for a remote configuration</h2><p><td >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.)</p><p>Click Configure to create a new server configuration or edit an existing one. (The Application Servers dialog will open.)</p><p><td >Select this checkbox to start a web browser after connecting to the server and deploying the artifacts.</p><p style=)
Select the browser from the list. Click 
.</p><p>Hot swap classes. Changed classes are recompiled and reloaded at runtime. This option works only in the debug mode.</p><p>Redeploy. The application artifact is rebuilt and redeployed.</p><p><td >Select this checkbox if you want to see the Update dialog every time you use the Update application function.</p><p>The Update dialog is used to select the Update option prior to actually updating the application.</p><p><td >Specify what IntelliJ > The options other than Do nothing have the same meanings as in the case of the Update action.</p><p>If you are not deploying anything with this run configuration, you don’t need to specify this port.</p><p>This section contains the settings related to staging. An example of remote staging settings for a mounted folder is provided after this table.</p><p><td >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 >connection type .)</p><p>The available options are:</p><p>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.</p><p>Local or mounted folder. The staging environment is a local folder or is accessed as a mounted folder.</p><p>If the list is empty, you have to enable the FTP/SFTP Connectivity plugin which supports the corresponding functionality.</p><p><td >If Same file system is selected for Type , the only available option for Host is also Same file system .</p><p>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.</p><p>Select an existing configuration or create a new one.</p><p>To create a new configuration: </p><ol></ol><p>Click to the right of the list.</p><p>In the Deployment dialog, click .</p><p>In the Add Server dialog, specify the configuration name, select the type, and click OK .</p><p> On the Connection tab, specify the settings in the Upload/download project files section.</p><p>The rest of the settings don’t matter.</p><p>Click OK in the Deployment dialog.</p><p><td >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.</p><p>Note that if Same file system is selected for Type and Host , no settings in this section need to be specified.</p><p><td >The path to the staging folder relative to the local or mounted folder, or the root of the (S)FTP host.</p><div style=)
.</p></li><li>Staging/Path from root: staging</li><li>Staging/Mapped as: C:\shared\staging</li></ul><h2>Deployment tab</h2><p>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.</p><p>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.</p><p>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:</p><p>is the server hostname (domain name) or IP address.</p><p>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.</p><p style=)
Use 
.</p><p>To specify the script, click and select the desired script in the dialog that opens.</p><p style=)
To specify the parameters, click , escape the double quotes by means of the backslashes, for example, -Dmy.prop=\»quoted_value\» .</p><p><td >Specify the script to be used to stop the server.</p><p><ul> If this checkbox is selected, the default script is used.</p></ul><p style=)
.</p><p>To specify the script, click and select the desired script in the dialog that opens.</p><p style=)
To specify the parameters, click , escape the double quotes by means of the backslashes, for example, -Dmy.prop=\»quoted_value\» .</p><p>Pass environment variables</p><p style=)
To add a variable, click 
Then, to move a configuration into a folder, between the folders or out of a folder, use drag or 
</p><p>Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.</p><p>By default this checkbox is selected and the Run or the Debug tool window opens when you start the run/debug configuration.</p><p>Otherwise, if the checkbox is cleared, 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 .</p><p><a href=)
источник