Revision as of 18:14, 5 February 2006

1. Use a JDBC database
2. Use Proxy Caching
3. Configure a default JDBC transaction-isolation
4. Add a configuration Function
5. Redirect a URL in the configuration file
6. Create a JMS Message Listener
7. Compress Servlet Output with GZip
8. Security Configuration
9. Configure a Virtual Host
10. Redirect System.out and System.err
11. Troubleshoot excessive garbage collection times
12. Use PHP
13. Specify error logs for each web-app
14. Alias a sub-url to a different directory
15. Include .asp pages
16. Delay listening to port 80 until after initialization
17. Add local configuration that survives .war redeployment
18. Select an XML Parser
19. Listen for server start and stop events
20. Replace Apache's mod_rewrite

Clustering and Load Balancing

1. Configure a Cluster Configuration Server
2. Configure Load Balancing
3. Select a particular backend server

web-apps

1. Assign a .war file for a web-app
2. Use one .war file for multiple web-apps
3. Restart a single web-app