The configuration and operation of the Sun Java System Web Server is controlled by configuration files. The configuration files reside in the directory instance_dir/config. This directory contains various configuration files for controlling different components. The exact number and names of configuration files depends on which components have been enabled or loaded into the server.
However, this directory always contains four configuration files that are essential for the server to operate. These files are:
server.xml -- contains most of the server configuration.
magnus.conf -- contains global server initialization information.
obj.conf -- contains instructions for handling HTTP requests from clients.
mime.types -- contains information for determining the content type of requested resources.
server.xmlfile contains most of the server configuration. A schema file, sun-web-server_6_1.dtd, defines its format and content.
For more information about how the server uses sun-web-server_6_1.dtd and server.xml, see Chapter 2, Server Configuration Elements in server.xml.
This file sets values of variables that configure the server during initialization. The server executes the settings in this file on startup. The server does not check at this file again until it is restarted.
See Chapter 3, Syntax and Use of magnus.conf for a list of all the variables and Init directives that can be set in magnus.conf.
This file contains instructions for the Sun Java System Web Server about how to handle HTTP requests from clients and service web server content such as native server plug-ins and CGI programs. The server checks the configuration defined by this file every time it processes a request from a client.
This file contains a series of instructions (directives) that tell the Sun Java System Web Server what to do at each stage in the request-response process.You can modify and extend the request handling process by adding or changing the instructions in obj.conf.
The maximum line length limit in obj.conf file is 800 characters.
All obj.conf files are located in the server_root/config directory. There is one obj.conf file for each virtual server class. Whenever this guide refers to "the obj.conf file," it refers to all obj.conf files or to the obj.conf file for the virtual server class described.
By default, each active obj.conf file is named vs_class-obj.conf. Editing one of these files directly or through the Administration interface changes the configuration of a virtual server class.
The obj.conf file is essential to the operation of the Sun Java System Web Server. When you make changes to the server through the Administration interface, the system automatically updates obj.conf.
For information about how the server uses obj.conf, see Chapter 4, Predefined SAFs in obj.conf.
This file maps file extensions to MIME types to enable the server to determine the content type of a requested resource. For example, requests for resources with .html extensions indicate that the client is requesting an HTML file, requests for resources with .gif extensions indicate that the client is requesting an image file in GIF format.
For more information about how the server uses mime.types, see "MIME Types."
For information about other important configuration files, see Chapter 6, Other Server Configuration Files.