- 5.1 The magnus.conf File
- 5.2 The server.xml File
- 5.3 The obj.conf File
- 5.4 The mime.types File
- 5.5 Trust Database Files (*.db Files)
- 5.6 The server.policy File
- 5.7 The certmap.conf File
- 5.8 The default.acl File
- 5.9 The default-web.xml File
- 5.10 The login.conf File
- 5.11 The keyfile File
- 5.12 Summary
- 5.13 Self-Paced Labs
5.13 Self-Paced Labs
Use the information contained in this chapter to perform the following exercises. These will help validate your understanding of the concepts described in this chapter.
- View the server.xml file for your default server installation. Do this for the files on the node, not beneath the admin-server instance.
- Locate the cluster element. What is the name of the host of this instance? (Look for the local-host element.)
- The instance element defines a member of the server cluster. What is the host name of the single instance that is part of this server cluster?
- Locate the log element. What is the logging level for this server instance, and where is the log file located on your file system?
- The platform element describes whether the server runs as a 32-bit or 64-bit process. As what platform does this server run?
Locate the user element (UNIX only). This is the system account the server runs as. As what account will the Web Server process run?
- Locate the auth-db element. This element replaces the functionality of dbswitch.conf from Web Server 6.1. What is the URL of the ACL authorization database?
- The auth-db element contains property elements. All property elements must contain the name and value subelements (for a name/value pair). They can also contain a description subelement and for auth-db they might contain the encoded subelement, indicating that the value is Base 64–encoded. List the name/value pairs for the property elements defined in the auth-db element.
- Locate the acl-file element. This element contains the name of the file that contains the access control list for this server instance. The value of this element can either be the absolute path to the file on the file system or the name of the file relative to the instance’s config folder. What is the name of the file that controls access to this instance and where is it located?
- Locate the mime-file element. This element contains the name of the file that contains the MIME types file used for request processing. What is the name of the file that contains the MIME type mappings, and where is it located?
- Web Server 6.1 listen sockets are referred to as Web Server 7.0 HTTP listeners. You define HTTP listeners by using the http-listener element. What subelements are defined for the HTTP listener for this server?
- Virtual servers are defined with the virtual-server element. Many of the elements that have been discussed thus far can be redefined within the body of a virtual-server element. This includes the auth-db, acl-file, and mime-file elements. Allowing the virtual server to redefine these elements provides the flexibility of having global settings for the server instance as well as localized settings for particular virtual servers. What subelements are defined for any virtual servers defined for this server?
Have these virtual servers redefined any of the global elements (auth-db, acl-file, or mime-file)? If so, which one(s)?
- Make a backup of the server.xml file for your default server instance. Download a copy of a corrupted server.xml file from the http://www.sunwebserver.com web site and place this file in the config directory for your default server instance. Update the downloaded server.xml file with information specific to your host and domain. Change all occurrences of the string, yourhost, with your actual hostname and all occurrences of the string, yourdomain, with your actual domain name. Restart the default Web Server instance and resolve all errors found when attempting to start the server. This step is completed when you have addressed all errors and the server successfully starts and serves up data. After you have completed this exercise, restore the backup copy of your server.xml file or use the Administration Console to overwrite the configuration on the node (do not pull the configuration from the node or you will overwrite the data in the config-store).