...
This stage creates a wrapper which allows tomcat to be managed as a service , which ; this allows it tomcat to be stopped and started reliably, and ensures that the running environment (e.g. the starting directory) is well defined.
Specifically, these instructions create a systemd service.
...
| Code Block |
|---|
[Unit]
Description=Apache Tomcat Web Application Container
After=network.target
[Service]
Type=forking
Environment=JAVA_HOME=/opt/jdk/jdk1.8.0_85/jre
Environment=CATALINA_PID=/opt/tomcat/temp/tomcat.pid
Environment=CATALINA_HOME=/opt/tomcat
Environment=CATALINA_BASE=/opt/tomcat
Environment='CATALINA_OPTS=-Xms1000M -Xmx2000M -server -verbose:gc'
Environment='JAVA_OPTS=-Djava.awt.headless=true'
ExecStart=/opt/tomcat/bin/startup.sh
ExecStop=/opt/tomcat/bin/shutdown.sh
WorkingDirectory=/opt/tomcat
User=tomcat
Group=tomcat
UMask=0007
RestartSec=10
Restart=always
[Install]
WantedBy=multi-user.target |
...
| Code Block |
|---|
sudo systemctl status tomcat |
Conclusion
From this point on, tomcat will start automatically when the host restarts, and you can re-start tomcat manually like this:
| Code Block |
|---|
sudo systemctl restart tomcat |