官术网_书友最值得收藏!

Configuration files and their usage

Apache Tomcat 7 comes with a default setup, which can be directly used for a QA environment. We can customize Tomcat based on the environment specification; components such as Services, Servers, Engine, Connectors, Realm, and Valve can be configured. The Tomcat configuration files are available in the conf folder. Let's discuss the configuration properties and their usage.

Tomcat 7, by default, comes with seven configuration files (usually in XML format), and these files are very useful in order to customize Tomcat, based on the environment needs. We shall install in the production or development environment.

The following screenshot shows the directory structure of the configuration directory for Tomcat 7:

Configuration files and their usage

It's very important from an administrator's point of view, to know about the configuration files and their usage in the Tomcat environment. Let's discuss the configuration properties one-by-one, as follows:

  • catalina.policy: This file describes the security policy permissions for Tomcat 7. It enforces the security policy permissions by JVM on the web application.

Note

When catalina is executed with the -security option, the security policy mentioned in the catalina file is used and the web application security policy also gets executed.

  • catalina.properties: This file contains the shared definition of the server, shared loader, and JARs, which need to be scanned at the time of the server startup.
  • server.xml: This is one of the important configuration files of Tomcat. It holds critical information, such as the IP address, port, virtual host, context path, and so on.
  • tomcat-users.xml: This file is used for authentication, authorization, and role-based definitions. It is used to implement a database of users/passwords/roles for authentication and container-managed security. To add/remove users or assign/unassign roles to existing users, edit this file.
  • logging.properties: As the name suggests, it defines the logging properties of the Tomcat instances (such as startup logs).
  • web.xml: This defines the default values for all web applications loaded into this instance of Tomcat, at the time of startup of the Tomcat instance. If a web application has its own deployment descriptor, its content will always override the configuration settings specified in this default descriptor.
  • context.xml: The contents of this file will load with every application. Configuration of parameters such as session persistence, Comet connection tracking, and so on, are done here.

Note

Any changes made in the server.xml file will be in effect after restarting the Tomcat instance.

Tip

Application level resources are not defined in the web.xml of the configuration folder. It would be better to define these in the application web.xml.

主站蜘蛛池模板: 高唐县| 唐山市| 岳普湖县| 蚌埠市| 德化县| 河西区| 会同县| 漳浦县| 德昌县| 武城县| 搜索| 屏南县| 乃东县| 凤城市| 巨野县| 崇义县| 惠来县| 乐亭县| 梨树县| 文昌市| 吴堡县| 滦平县| 乐安县| 建阳市| 开化县| 泰来县| 葫芦岛市| 崇仁县| 钟祥市| 蓬莱市| 天峨县| 昭觉县| 桑植县| 南雄市| 英德市| 新巴尔虎右旗| 琼海市| 丰城市| 廊坊市| 苍溪县| 泰顺县|