...
That's pretty much the setup that I'm doing going to use.
Installing the .war file to run
Tomcat runs .war files - self-contained web archive files that contain your web application. You don't really install these, just simply copy it to /opt/tomcat/webapps/ROOT.war
For example (if I had a .war file in my home folder):
| Code Block |
|---|
sudo cp ~/my.war /opt/tomcat9/webapps/ROOT.war |
Running Tomcat
We can now start Tomcat. You can do this by runing the startup.sh script in /opt/tomcat/bin, or use catalina.sh run:
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
# Properties for use with AWS Elastic Beanstalk (see documentation)
# set application profile
spring.profiles.active=PROD
# Logging level of SQL run. Change to DEBUG to print out SQL statements into logs
logging.level.org.hibernate.SQL=INFO
# Logging level of values passed to SQL statements. Change to TRACE to print out values in logs
logging.level.org.hibernate.type.descriptor.sql.BasicBinder=INFO
# use component ids for client-server communication (for load testing, false by default)
loadtestmode.enabled=false
#
logging.level.com.vaadin.spring.navigator.SpringViewProvider=WARN
logging.level.com.vaadin.spring.server.SpringUIProvider=WARN
# No need to presist sessions
server.session.persistent=false
# Put Vaadin into production mode
vaadin.servlet.productionMode=true
# Use MySQL production db
spring.jpa.hibernate.ddl-auto=update
spring.datasource.url=jdbc:mysql://${MYSQL_HOSTNAME}:${MYSQL_PORT}/${DB_NAME}
spring.datasource.username=${USERNAME}
spring.datasource.password=${PASSWORD}
spring.jpa.properties.hibernate.dialect=org.hibernate.dialect.MySQL5Dialect
|
...