Apache Tomcat 8

Tomcat Setup

Table of Contents

Introduction

There are several ways to set up Tomcat for running on different platforms. The main documentation for this is a file called RUNNING.txt. We encourage you to refer to that file if the information below does not answer some of your questions.

Windows

Installing Tomcat on Windows can be done easily using the Windows installer. Its interface and functionality is similar to other wizard based installers, with only a few items of interest.

• Installation as a service: Tomcat will be installed as a Windows service no matter what setting is selected. Using the checkbox on the component page sets the service as «auto» startup, so that Tomcat is automatically started when Windows starts. For optimal security, the service should be run as a separate user, with reduced permissions (see the Windows Services administration tool and its documentation).
• Java location: The installer will provide a default JRE to use to run the service. The installer uses the registry to determine the base path of a Java 7 or later JRE, including the JRE installed as part of the full JDK. When running on a 64-bit operating system, the installer will first look for a 64-bit JRE and only look for a 32-bit JRE if a 64-bit JRE is not found. If a JRE cannot be found when running on a 64-bit operating system, the installer will look for a 64-bit JDK. Finally, if a JRE or JDK has not been found, the installer will try to use the JAVA_HOME environment variable. It is not mandatory to use the default JRE detected by the installer. Any installed Java 7 or later JRE (32-bit or 64-bit) may be used.
• Tray icon: When Tomcat is run as a service, there will not be any tray icon present when Tomcat is running. Note that when choosing to run Tomcat at the end of installation, the tray icon will be used even if Tomcat was installed as a service.
• Defaults: The defaults used by the installer may be overridden by use of the /C= command line argument. The configuration file uses the format name=value with each pair on a separate line. The names of the available configuration options are:
  • JavaHome
  • TomcatPortShutdown
  • TomcatPortHttp
  • TomcatMenuEntriesEnable
  • TomcatShortcutAllUsers
  • TomcatServiceDefaultName
  • TomcatServiceName
  • TomcatServiceFileName
  • TomcatServiceManagerFileName
  • TomcatAdminEnable
  • TomcatAdminUsername
  • TomcatAdminPassword
  • TomcatAdminRoles

  By using /C=. along with /S and /D= it is possible to perform fully configured unattended installs of Apache Tomcat.

• Refer to the Windows Service How-To for information on how to manage Tomcat as a Windows service.

The installer will create shortcuts allowing starting and configuring Tomcat. It is important to note that the Tomcat administration web application can only be used when Tomcat is running.

Unix daemon

Tomcat can be run as a daemon using the jsvc tool from the commons-daemon project. Source tarballs for jsvc are included with the Tomcat binaries, and need to be compiled. Building jsvc requires a C ANSI compiler (such as GCC), GNU Autoconf, and a JDK.

Before running the script, the JAVA_HOME environment variable should be set to the base path of the JDK. Alternately, when calling the ./configure script, the path of the JDK may be specified using the —with-java parameter, such as ./configure —with-java=/usr/java .

Using the following commands should result in a compiled jsvc binary, located in the $CATALINA_HOME/bin folder. This assumes that GNU TAR is used, and that CATALINA_HOME is an environment variable pointing to the base path of the Tomcat installation.

Please note that you should use the GNU make (gmake) instead of the native BSD make on FreeBSD systems.

Tomcat can then be run as a daemon using the following commands.

When running on Java 9 you will need to additionally specify the following when starting jsvc to avoid warnings on shutdown.

You may also need to specify -jvm server if the JVM defaults to using a server VM rather than a client VM. This has been observed on OSX.

jsvc has other useful parameters, such as -user which causes it to switch to another user after the daemon initialization is complete. This allows, for example, running Tomcat as a non privileged user while still being able to use privileged ports. Note that if you use this option and start Tomcat as root, you’ll need to disable the org.apache.catalina.security.SecurityListener check that prevents Tomcat starting when running as root.

jsvc —help will return the full jsvc usage information. In particular, the -debug option is useful to debug issues running jsvc.

Apache Tomcat 8

Windows service HOW-TO

Table of Contents

Tomcat service application

Tomcat8 is a service application for running Tomcat 8 as a Windows service.

Tomcat monitor application

Tomcat8w is a GUI application for monitoring and configuring Tomcat services.

The available command line options are:

//ES//	Edit service configuration	This is the default operation. It is called if the no option is provided but the executable is renamed to servicenameW.exe
//MS//	Monitor service	Put the icon in the system tray

Command line arguments

Each command line directive is in the form of //XX//ServiceName

The available command line options are:

//TS//	Run the service as console application	This is the default operation. It is called if the no option is provided. The ServiceName is the name of the executable without exe suffix, meaning Tomcat8
//RS//	Run the service	Called only from ServiceManager
//SS//	Stop the service
//US//	Update service parameters
//IS//	Install service
//DS//	Delete service	Stops the service if running

Command line parameters

Each command line parameter is prefixed with —. If the command line parameter is prefixed with ++ then it’s value will be appended to the existing option. If the environment variable with the same name as command line parameter but prefixed with PR_ exists it will take precedence. For example:

is equivalent to providing

as command line parameter.

ParameterName	Default	Description
—Description	Service name description (maximum 1024 characters)
—DisplayName	ServiceName	Service display name
—Install	procrun.exe //RS//ServiceName	Install image
—Startup	manual	Service startup mode can be either auto or manual
—DependsOn	List of services that this service depend on. Dependent services are separated using either # or ; characters
—Environment	List of environment variables that will be provided to the service in the form key=value. They are separated using either # or ; characters. If you need to use either the # or ; character within a value then the entire value must be enclosed inside single quotes.
—User	User account used for running executable. It is used only for StartMode java or exe and enables running applications as service under account without LogonAsService privilege.
—Password	Password for user account set by —User parameter
—JavaHome	JAVA_HOME	Set a different JAVA_HOME than defined by JAVA_HOME environment variable
—Jvm	auto	Use either auto (i.e. find the JVM from the Windows registry) or specify the full path to the jvm.dll. You can use the environment variable expansion here.
—JvmOptions	-Xrs	List of options in the form of -D or -X that will be passed to the JVM. The options are separated using either # or ; characters. If you need to embed either # or ; characters, put them inside single quotes. (Not used in exe mode.)
—JvmOptions9	List of options in the form of -D or -X that will be passed to the JVM when running on Java 9 or later. The options are separated using either # or ; characters. If you need to embed either # or ; characters, put them inside single quotes. (Not used in exe mode.)
—Classpath	Set the Java classpath. (Not used in exe mode.)
—JvmMs	Initial memory pool size in MB. (Not used in exe mode.)
—JvmMx	Maximum memory pool size in MB. (Not used in exe mode.)
—JvmSs	Thread stack size in KB. (Not used in exe mode.)
—StartMode	One of jvm, Java or exe. The modes are: jvm — start Java in-process. Depends on jvm.dll, see —Jvm. Java — same as exe, but automatically uses the default Java executable, i.e. %JAVA_HOME%\bin\java.exe. Make sure JAVA_HOME is set correctly, or use —JavaHome to provide the correct location. If neither is set, procrun will try to find the default JDK (not JRE) from the Windows registry. exe — run the image as a separate process
—StartImage	Executable that will be run. Only applies to exe mode.
—StartPath	Working path for the start image executable.
—StartClass	Main	Class that contains the startup method. Applies to the jvm and Java modes. (Not used in exe mode.)
—StartMethod	main	Method name if differs then main
—StartParams	List of parameters that will be passed to either StartImage or StartClass. Parameters are separated using either # or ; character.
—StopMode	One of jvm, Java or exe. See —StartMode for further details.
—StopImage	Executable that will be run on Stop service signal. Only applies to exe mode.
—StopPath	Working path for the stop image executable. Does not apply to jvm mode.
—StopClass	Main	Class that will be used on Stop service signal. Applies to the jvm and Java modes.
—StopMethod	main	Method name if differs then main
—StopParams	List of parameters that will be passed to either StopImage or StopClass. Parameters are separated using either # or ; character.
—StopTimeout	No Timeout	Defines the timeout in seconds that procrun waits for service to exit gracefully.
—LogPath	%SystemRoot%\System32\LogFiles\Apache	Defines the path for logging. Creates the directory if necessary.
—LogPrefix	commons-daemon	Defines the service log filename prefix. The log file is created in the LogPath directory with .YEAR-MONTH-DAY.log suffix
—LogLevel	Info	Defines the logging level and can be either Error, Info, Warn or Debug. (Case insensitive).
—StdOutput	Redirected stdout filename. If named auto then file is created inside LogPath with the name service-stdout.YEAR-MONTH-DAY.log.
—StdError	Redirected stderr filename. If named auto then file is created inside LogPath with the name service-stderr.YEAR-MONTH-DAY.log.
—PidFile	Defines the file name for storing the running process id. Actual file is created in the LogPath directory

Installing services

The safest way to manually install the service is to use the provided service.bat script. Administrator privileges are required to run this script. If necessary, you can use the /user switch to specify a user to use for the installation of the service.

NOTE: On Windows Vista or any later operating system with User Account Control (UAC) enabled you will be asked for additional privileges when ‘Tomcat8.exe’ is launched by the script.
If you want to pass additional options to service installer as PR_* environment variables, you have to either configure them globally in OS, or launch the program that sets them with elevated privileges (e.g. right-click on cmd.exe and select «Run as administrator»; on Windows 8 (or later) or Windows Server 2012 (or later), you can open an elevated command prompt for the current directory from the Explorer by clicking on the «File» menu bar). See issue 56143 for details.

There is a 2nd optional parameter that lets you specify the name of the service, as displayed in Windows services.

If using tomcat8.exe, you need to use the //IS// parameter.

Установка Tomcat на Windows

Установка Tomcat на Windows

Хотите узнать, как установить службу Tomcat на компьютер под управлением Windows? В этом учебнике мы покажем вам, как установить Tomcat на компьютер под управлением Windows.

Windows 2012 R2
• Windows 2016
— Windows 2019

Плейлист Windows:

На этой странице мы предлагаем быстрый доступ к списку видео, связанных с установкой Windows.

Не забудьте подписаться на наш канал YouTube под названием FKIT.

Windows Учебник:

На этой странице мы предлагаем быстрый доступ к списку учебников для Windows.

Учебник Tomcat — Установка требований

Получите доступ к веб-сайту Java и загрузите последнюю версию Java JDK.

В нашем примере мы скачали файл под названием: jdk-14.0.1_windows-x64_bin.exe

Запуск установки Java JDK.

Нажмите на кнопку «Следующая».

Дождитесь завершения установки Java JDK.

В нашем примере программное обеспечение Java JDK было установлено на следующем каталоге.

В качестве администратора запустите новый запрос командной строки POWERSHELL.

Создайте переменную системной среды, названную JAVA_HOME.

Измените приведенную выше команду, чтобы отразить ваш путь установки JDK.

Теперь нам нужно редактировать переменную среды PATH.

Включите каталог Java SDK под названием BIN в переменную среды PATH.

Поздравляю! Вы закончили установку Java JDK на Windows.

Tutorial Tomcat — Тестирование установки Java SDK

Запустите новый запрос командной строки DOS.

Проверьте наличие переменной JAVA_HOME.

Вот вывод команды.

Проверьте java-приложение с помощью переменной, названной JAVA_HOME.

Вот вывод команды.

Проверить, включает ли переменная среды PATH каталог Java SDK под названием BIN.

Вот вывод команды.

Проверьте Java-приложение без использования переменной среды.

Вот вывод команды.

Поздравляю! Вы протестировали установку Java JDK на Windows.

Учебная windows — установка Tomcat

Получите доступ к веб-сайту Apache Tomcat и загрузите последнюю версию Tomcat.

В нашем примере мы скачали файл под названием: Apache-tomcat-9.0.37.exe

Запустите установку Tomcat.

Выберите опцию Hostmanager и нажмите на кнопку «Следующая».

Установите имя пользователя и пароль администратора Tomcat.

Дополнительно можно изменить порт TCP.

Установите путь установки Java JDK и нажмите на кнопку «Следующая».

В нашем примере установщик Tomcat автоматически обнаружил каталог установки Java SDK.

Проверьте путь установки Tomcat и нажмите на кнопку «Следующая».

В нашем примере программное обеспечение Tomcat было установлено на следующем каталоге.

Нажмите на кнопку Установки и дождитесь завершения установки Tomcat.

Выберите опцию запуска сервиса Tomcat и нажмите на кнопку «Финиш».

Откройте браузер и введите IP-адрес вашего сервера Tomcat плюс :8080.

В нашем примере в браузер был введен следующий URL::

Страница Tomcat должна быть представлена.

Поздравляю! Вы закончили установку Tomcat на Windows.