Application wide settings

Application-wide settings are made depending on the choosen type of deployment:

• Environmental variables: This method is useful for containerized deployments as environmental variables can be defined in the container configuration.

Example for environmental variables in a docker command:

docker run 
  [..] 
  -e TIA_LICENSE_PATH=/application/config/tialic 
  -e LOGGING_LEVEL_ROOT=ERROR
  -e WEBAPP_SECURITY_AUTH_BASIC_USERNAME=admin 
  -e WEBAPP_SECURITY_AUTH_BASIC_PASSWORD="\$2a\$10\$JKRQvv.bCNjlyLoBqORAq.79SlwpD8h9nWoo9ss35vt2Pi11KJ2B."
  [..] 

• Java command line parameters: In a war-file deployment, the web application server is a Java application and therefore started by a java command line.

Example:

java -D"logging.config"="my.log4j2.xml" [..]

• In Tomcat context file: This is useful for a war-file deployment in a web application server. The context file is a XML file with the same name as the web application context (respective the war-file deployed. E.g. autodigit.xml) and is located in <tomcat installation>/conf/Catalina/localhost directory. For more information see Apache Tomcat documentation: https://tomcat.apache.org/tomcat-10.0-doc/config/context.html.

Example for Tomcat context file:

<?xml version="1.0" encoding="UTF-8"?> 
<!DOCTYPE Context> 
  <Context>     
     <Parameter 
          name="logging.level.com.software.kgs"         
          value="info" 
          override="true" />      
     <Parameter     
          name="logging.config" 
          value="C:/Program Files/tomcat/webapps/coreoftia/META-INF/my.log4j2.xml" 
          override="true" />
  </Context>         

The parameter names are written in lowercase strings and reflect the hierarchy of application modules. For that reason, the . (dot character) is used to separate the levels in the hierarchy.