Sun Java System Web Server 7.0 Update 4 Administrator's Configuration File Reference

Chapter 1 Overview of Configuration Files and Directories

The configuration and behavior of Sun Java System Web Server 7.0 (Web Server) is determined by a set of configuration files. You can use the Admin Console and the command-line interface (CLI) to change the configuration file settings. You can also manually edit these files.

This chapter has the following sections:

Configuration Files

Each server instance has its own directory, called instance_dir in this document. The instance_dir/config directory contains configuration files for the Web Server components. The exact number and names of the configuration files depend on the components that have been enabled or loaded into the server. For the default location of the instance_dir, see Default Paths and File Names.

These files, as well as some other configuration files not included in the config directory, are described in the following sections:

The server.xml File

The server.xml file contains most of the server configuration. A schema file, sun-web-server_7_0.xsd, validates its format and content. For more information about sun-web-server_7_0.xsd and the various elements of server.xml, see Chapter 2, Syntax and Use of server.xml and Chapter 3, Elements in server.xml.

The magnus.conf File

The magnus.conf file contains the NSAPI plug-in initialization directives and settings that control the way NSAPI plug-ins are run. For more information about magnus.conf, see Chapter 4, Syntax and Use of magnus.conf and Chapter 5, Predefined SAFs in magnus.conf.

The obj.conf File

The obj.conf file contains directives for HTTP request processing. For more information about obj.conf, see Chapter 6, Syntax and Use of obj.conf and Chapter 7, Predefined SAFs and Filters in obj.conf.

The mime.types File

The mime.types 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, while requests for resources with .gif extensions indicate that the client is requesting an image file in GIF format. For more information about mime.types, see Chapter 8, MIME Types.

ACL Files

The Access Control List (ACL) files contain lists that define who can access resources stored on your Web Server. By default, Web Server uses one ACL file. You can create multiple ACL files and reference them in the obj.conf and server.xml files. For more information about ACL files, see Chapter 9, ACL Files.

Other Configuration Files

Other configuration files for administration and for applications include the certmap.conf, sun-web.xml, login.conf, server.policy, and default-web.xml. For more information on these files, see Chapter 10, Other Server Configuration Files.

Directory Structure

This section describes the directory structure that is created when you first install Sun Java System Web Server. In a stand-alone Web Server installation, all these directories are in the install_dir by default. In Web Servers installed as part of Java Enterprise System, the instance directories (which in this case includes both admin-sever and https-sever_id) are in a different location. For more information on the default locations for these directories on different platforms, see the information on instance_dir in Default Paths and File Names.


The admin-server directory has the following subdirectories:


The bin directory contains the binary files for administering Web Server. These files include wadm, the administration command-line interface (CLI).


An https-server_id directory is created for every instance you create. This directory has the following subdirectories and files:


The include directory contains the various include files, for example, NSAPI and SHTML include files.


The jdk directory contains the bundled Java development kit (JDKTM). For stand-alone installations only.


The lib directory contains internal binaries, scripts, libraries, and bundled plug-ins. These files are private files, for internal use only.


The plugins directory contains the plug-in subdirectories. .

For more information on these plug-ins, see Sun Java System Web Server 7.0 Update 4 Administrator’s Guide.


The samples directory contains samples and example components, plug-ins, and technologies supported by the Sun Java System Web Server Servlet engine. This includes binaries, all code, and a build environment.


The setup directory contains the various Web Server setup files, including the installation logs.

Dynamic Reconfiguration

Dynamic reconfiguration allows you to make configuration changes to a runtime Web Server. You do not have to stop or restart the Web Server for the changes to take effect.

Dynamic configuration happens in one of the following ways:

You can dynamically change the configuration settings in the obj.conf, mime.types, and ACL files without restarting the server. In addition, most settings in the server.xml file can be changed without restarting the server. If a server restart is required, a warning message appears in the server log when you deploy the configuration or run the reconfig command.

You cannot dynamically reconfigure the following server.xml configuration parameters:

When you run the reconfig command, a new configuration object is created and allnew incoming requests are processed based on this new configuration object. The current configuration object gets removed when no HTTP requests are using the object. For example, if you are using Web Server with reverse proxy in the front-end can dynamically add a new back-end server and apply the reconfiguration by using the reconfig command.

The following additional configuration changes within server.xml are supported by the reconfig command:

Note –

Some configuration changes cannot be instantly propogated to the running server. For example, adding a JVM property of a resource.

If a misconfiguration occurs during dynamic reconfiguration, the server displays an error message. The server logs the error message to a log file specified by the previous known good configuration.

Certain misconfigurations result in warning messages but do not cause the server to reject the configuration. Other misconfigurations result in error messages and cause the server to reject the configuration. If the server rejects a configuration during startup, the server does not start. If the server rejects a configuration during dynamic reconfiguration, the server reverts to the previous known good configuration.