In previous releases, server configuration was spread over multiple files. In Web Server 7.0, server configuration has been consolidated for better manageability. Many changes have been made to consolidate instance-specific configuration files in the config directory and to simplify and enhance existing configuration files. In general, no new configuration files have been added, some configuration files have been removed, and significant changes have been made to files carried forward from previous releases, such as server.xml and magnus.conf.
Some configuration file changes are briefly mentioned here but are not described in detail. For complete information about configuration file changes in Web Server 7.0, see the Web Server 7.0 Administrator's Configuration File Reference.
The following configuration files have been removed in Web Server 7.0:
dbswitch.conf
nsfc.conf
scheduler.conf
schedulerd.conf
snmp.conf
For more information, see File Layout Changes.
The following table lists file layout changes between Sun Java System Web Server 6.1 and Web Server 7.0. These changes are made automatically during migration.
For information about changes made in Sun Java System Web Server 6.1 and earlier product versions, see the latest Sun Java System Web Server 6.1 documenation collection at http://docs.sun.com/prod/sjs.websrv61#hic.
Table 5–1 File Layout Changes
Web Server 6.1 |
Web Server 7.0 |
---|---|
install_root/alias/https-server_id-hostname-certx.db |
install-dir/https-server_id/config/certx.db, where x=7 or 8 (Web Server 7.0 supports both cert7 and cert8) |
install_root/alias/https-server_id-hostname-key3.db |
install-dir/https-server_id/config/key3.db |
install_root/alias/secmod.db |
install-dir/https-server_id/config/secmod.db |
install_root/httpacl/generated.https-server_id.acl |
install-dir/https-server_id/config/default.acl |
install_root/httpacl/genwork.https-server_id.acl |
Removed |
install_root/userdb/certmap.conf |
install-dir/https-server_id/config/certmap.conf |
install_root/userdb/dbswitch.conf |
Removed; functionality moved to the auth-db element in server.xml. |
instance-dir/config/nsfc.conf |
Removed; functionality moved to the file-cache element in server.xml. |
instance-dir/config/snmp.conf |
Remove; functionality moved to the snmp element in server.xml. |
admsrv_dir/config/scheduler.conf |
Removed; functionality moved to the event element in server.xml and entries migrated to Web Server 7.0 (no manual changes are required). |
admsrv_dir/config/schedulerd.conf |
Removed |
instance-dir/config/*.clfilter |
Removed |
instance-dir/config/magnus.conf |
install-dir/https-server_id/config/magnus.conf Retained for NSAPI plug-in configuration, but all functionality not related to NSAPI plug-ins has been moved to server.xml. Support for some obsolete directives has been dropped. The magnus.conf file is copied into the new server configuration during migration. If any removed or obsolete directives are found, a warning is issued. The following new elements will be created in server.xml:
For detailed information about these changes, see the Web Server 7 Administrator's Configuration File Reference. |
instance-dir/config/obj.conf |
install-dir/https-server_id/config/obj.conf Retained. In Web Server 6.1, all virtual servers within a given VSCLASS shared a common obj.conf. In Web Server 7.0, each virtual server can have its own obj.conf, or can still share the same obj.conf. For detailed information about these changes, see Chapter 6, Syntax and Use of obj.conf, in Oracle iPlanet Web Server 7.0.9 Administrator’s Configuration File Reference and Chapter 2, Configuration, Instances, and Nodes, in Oracle iPlanet Web Server 7.0.9 Administrator’s Guide |
instance-dir/config/server.xml |
install-dir/https-server_id/config/server.xml Most of the attribute names have changed. Some elements have been consolidated and some have split. For detailed information about these changes, see the Web Server 7.0 Administrator's Configuration File Reference. The Web Server 6.0 or 6.1 server.xml file is parsed and the values written in the new server.xml file, which is created during migration. |
server_instance/config/mime.types |
install-dir/https-server_id/config/mime.type During migration, the mime.types file of the old instance in the server_instance/config/mime.types directory is migrated into the new server_instance/config directory. Non-default mime.types (mime1.types, mime2.types, and so on) in the old server_instance/config directory and listed in the MIME element of server.xml are migrated into the new server_instance/config directory. |