Как запустить tomcat в intellij idea
We’re going to create a small web application that runs on Tomcat to demonstrate the integration in IntelliJ IDEA Ultimate:
- From the Welcome Screen select New Project.
- If you have an existing project open, click File > New. Select Java Enterprise on the left-hand menu and enter the following details:
| Field Name | Description |
|---|---|
| Name | The name of your project, such as HelloWebApp . |
| Location | The location of your project. |
| Create Git repository | Select this checkbox if you want to use Git to version control the files in this project. |
| Template | We want to create a RESTful web application so leave the REST service template selected. |
| Application Server | Select New > Tomcat Server. For the Tomcat Home, browse to the directory where you have Tomcat installed. This will also populate the Tomcat base directory. Click OK. |
| Language | This blog post uses Java. |
| Build System | This blog post uses Maven. |
| Group | You can change this if required or leave it as the default com.example . |
| Artifact | This is the name of your project by default. You don’t need to change it. |
| JDK | I’m using JDK 17 for this blog post. |
- Click Next to go to the next step in the tutorial and select Jakarta EE 9 from the Version drop-down. The Eclipse Jersey Server and Weld SE have been preselected for us because we selected REST service as the template in the previous step.
- Click Create to set up the project. IntelliJ IDEA will now create our simple web application which will output “Hello, World!” when it receives a GET request.
You can open the Services window with ⌘8 (macOS) / Alt+8 (Windows/Linux) to see the Tomcat server we just configured along with our web application.
We can run our application with ⌃⇧R (macOS) / Ctrl+Shift+F10 (Windows/Linux) and this starts our Tomcat server. In the Run window ⌘4 (macOS), Alt+4 (Windows/Linux), you can check the logs to ensure that your Tomcat server is being deployed, however, IntelliJ IDEA automatically opens a browser when the URL of the application’s root context — http://localhost:8080/HelloWorldApp_war_exploded/. You should receive a 404 error:
We get this 404 page because Tomcat is running and listening for requests, but our application has no view to display. For example, we don’t currently have an index.jsp file. (because it’s a simple service with some REST APIs). In the next step, we will figure out how to reach our application’s endpoint that displays the Hello World message.
If we go back to our application code, we can find the ApplicationPath in our HelloApplication.java — which is /api . In addition, in our HelloResource.java file, our Path is set to /hello-world . This means we can make a GET request to the HelloResource by adding api/hello-world to the URL in my browser making the full URL: http://localhost:8080/HelloWorldApp_war_exploded/api/hello-world.
Now you will be able to see Hello World printed out in your browser:
Русские Блоги
Руководство по настройке 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 в обычном режиме. 
Интеллектуальная рекомендация
Используйте Intellij Idea Community Edition для разработки сервлета
2019 Encorn Enterprise Recruitment Python Engineer Standard >>> В нескольких Java IDE IntelliJ Idea должна быть наиболее одобряющей глаз, но бесплатная версия сообщества не может быть оснащен.
Установить Intellij Idea Community Edition в Linux
1. Загрузите версию сообщества Idea на официальном сайте http://www.jetbrains.com 2. Десятилетие 3. Используйте команду CD, чтобы войти в мусорное ведро, запустите идею .
Новая версия руководства по настройке IDEA для Tomcat (2018)
Моя версия: IntelliJ IDEA Community Edition 2018.1.2 Я долго не находил соответствующий сервер в том месте, где был настроен сервер Tomcat, но в отчаянии я использовал метод файла конфигурации. 1. Доб.
Руководство по загрузке и установке MySQL Community Edition
Руководство по загрузке и установке MySQL Community Edition 1. Скачать В этом руководстве демонстрируется версия сжатого пакета MySQL8 Community Edition. Щелкните следующую ссылку, чтобы перейти на ст.
IntelliJ IDEA — запуск / отладка веб-приложения на Tomcat
В этой статье показано, как запустить или отладить веб-приложение на сервере Tomcat, используя IntelliJ IDEA.
Заметка
В отличие от Eclipse IDE, всегда есть «представление сервера» для настройки сервера добавления, IntelliJ делает все по-другому, сначала нужно добавить «артефакт (военный файл)», тогда только внизу будет отображаться «представление сервера» ,
1. Tomcat Плагин
1.1 Файл — >> Настройки — >> Плагин типа — >> Убедитесь, что включена интеграция Tomcat и TomEE.
2. Запуск / отладка конфигурации
2.1 Выполнить — >> Редактировать конфигурации …
2.2 Клики + значок, выберите Tomcat Server — >> Локальный
ЧИТАТЬ ТАКЖЕ: Как установить MongoDB на Mac OS X
3. Конфигурация Tomcat
3.1 Нажмите на вкладку «Развертывание», значок +, чтобы выбрать артефакт для развертывания. Для отладки точки останова всегда выбирайте версию войны в разобранном виде.
3.2 Нажмите на вкладке «Сервер», выберите сервер Tomcat и обновите on ‘Update’ action «Обновлять классы и ресурсы» — для горячей замены.
4. Серверы приложений
4.1 Теперь на нижней панели отображается вид «Серверы приложений».
Запустите или отладьте ваше веб-приложение, готово.
Run/Debug Configuration: Tomcat Server
Use the Tomcat Server run/debug configuration to deploy and debug your applications on Tomcat. For more information, refer to Application server run configurations.
- Use a Local configuration to run a local instance of the application server and deploy the artifacts to it.
- Use a Remote configuration to deploy artifacts to a running application server instance. Even if you are connecting to a remote application server, you still need a local installation of this server configured under Build, Execution, Deployment | Application Servers as described in Integration with application servers.
Enable the Tomcat and TomEE plugin
This functionality relies on the Tomcat and TomEE plugin, which is bundled and enabled in IntelliJ IDEA by default. If the relevant features aren’t available, make sure that you didn’t disable the plugin.
- Press Control+Alt+S to open the IDE settings and then select Plugins .
- Open the Installed tab, find the Tomcat and TomEE plugin, and select the checkbox next to the plugin name.
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.
Specify the options to be passed to the Java virtual machine when launching the application, for example, -mx , -verbose , and so on.
When specifying JVM options, follow these rules:
- Use spaces to separate individual options.
- If the value of an option includes spaces, enclose either the value or the actual spaces with double quotes.
- If an option includes double quotes as part of the value, escape the double quotes using backslashes.
- You can pass environment variable values to custom Java properties.
-Xmx1024m -Dspaces=»some arg» -Dmy.prop=\»quoted_value\» -Dfoo=$
Use code completion in this field: start typing the name of a flag, and the IDE suggests a list of available command line options. This works for -XX: and -X options and some standard options that are not configured by IntelliJ IDEA automatically, like -ea , but not for -cp or –release .
The -classpath option specified in this field overrides the classpath of the module.
On ‘Update’ action
Select the necessary option for the Update application function ( or Control+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 Control+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.
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.
- ftp. The File Transfer Protocol or Secure FTP is used.
- 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 Deployment dialog, click .
- 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.
Example: remote staging 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
Specify which artifacts or external resources to deploy. An external resource is 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 deploy artifacts to a remote application server, you need Tomcat version 5 or later. Make sure that you pass the following VM options to enable JMX support on the server:
-Dcom.sun.management.jmxremote= -Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.rmi.port=1099 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.rmi.server.hostname=127.0.0.1
Specify the port and hostname or IP address of your application server.
If you use catalina.bat or catalina.sh to start the server, pass the options via 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 multiple instances
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.
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.
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.
Before launch
In this area, you can specify tasks to 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:
- 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, refer to External tools and External tools settings.
- Run Another Configuration : select to execute another run/debug configuration and wait until it finishes before starting the current configuration. If you want to run several configurations in parallel, use a compound run/debug configuration.
- 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.
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.
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 .