This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
When running Tomcat applications in Linux App Service using built-in Java Tomcat docker image, sometime you may need to customize your Tomcat configuration.
In this blog, we will provide detailed steps of how to modify the default server.xml file in the built-in docker container.
Before trying to overwrite the existing server.xml, please make sure whether it's possible to make your configuration changes in context.xml or web.xml.
- server.xml: This file includes general configuration of Tomcat server. For each Tomcat server, we can only find one $CATALINA_BASE/conf/server.xml file.
- context.xml: This file contains server-dependent configuration like DataSources provided by Tomcat server.
- This file can be stored in the $CATALINA_BASE/conf/context.xml: the Context element information will be loaded by all web applications.
- It can also be stored in $webapp_base/META-INF/context.xml: the Context element information will be loaded by the specific web application.
- web.xml: This file contains server-independent configuration like servlet mappings.
- This file can be stored in the $CATALINA_BASE/conf/web.xml, which may be configured for use with all web applications.
- It can also be stored in $webapp_base/WEB-INF/web.xml, which may be configured for individual web applications.
Reference doc:
https://tomcat.apache.org/tomcat-9.0-doc/config/server.html
https://tomcat.apache.org/tomcat-9.0-doc/config/context.html
https://tomcat.apache.org/tomcat-9.0-doc/config/filter.html
There are two options that you can use to modify the built-in server.xml file in App Service built-in Java Tomcat docker image.
- Completely overwrite the built-in server.xml file with you own server.xml.
This method is simple and straightforward. But if App Service platform upgrades in the future, there will be potential risks that your own server.xml may encounter compatibility issue with our platform. - Use xsl transform to modify the built-in server.xml with necessary and minimum changes.
This method is a little bit complex, but it can minimize the potential compatibility issue during App Service platform upgrades.
Completely overwrite the built-in server.xml file with you own server.xml
1. Go to WEBSSH, https://<webapp-name>.scm.azurewebsites.net/webssh/host
2. Copy the built-in server.xml file to any place under /home
3. Directly make change to /home/server.xml file
4. Create your customer startup script in any place under /home
The contents of the startup.sh file should include the followings:
5. Go to Configuration portal to set "Startup Command", point it to your /home/startup.sh
Use xsl transform to modify the built-in server.xml with necessary and minimum changes
1. Go to WEBSSH, https://<webapp-name>.scm.azurewebsites.net/webssh/host
2. Use cat command to get the contents of the built-in server.xml file
Copy the file contents into your Notepad on your local machine. Later you can put the server.xml content into online XSL test tool (e.g. https://www.freeformatter.com/xsl-transformer.html) to test your XSL transform file.
3. Write xsl transform file, which can be used to transfer the server.xml contents
For example: I can use the following xsl file to modify my Tomcat access log format (add original client IP address in the log file).
Original XML contents:
Sample transform.xsl file:
Modified XML contents:
Note:
- How to use XSL transform?
Reference doc: https://www.w3schools.com/xml/xsl_intro.asp - We can use online XSL test tools to verify whether it can modify the server.xml as expected.
e.g. https://www.freeformatter.com/xsl-transformer.html
4. Upload your transform.xsl file to anywhere under /home folder.
Go to https://<webapp-name>.scm.azurewebsites.net/newui/fileManager
5. Create your customer startup script anywhere under /home (e.g. /home/startup.sh)
The contents of the startup.sh file should include the followings:
6. Go to Configuration portal to set "Startup Command", point it to your /home/startup.sh