Master IIS6.0 function and application detailed graphics and text tutorial two 1/4 page _ server

Second, configuration data

In IIS 5.0 and IIS 4.0, the configuration database takes the binary file structure, but IIS 6.0 discards this practice. The configuration data for IIS 6.0 consists of two XML files: One is MetaBase.xml, contains configuration information for IIS 6.0 servers, and the other is MBSchema.xml, which contains schema definitions for configuration data. IIS Manager provides a new feature that allows you to save a copy of your configuration data by right-clicking the Web site and selecting All Tasks → save configuration to a file, and then specifying the file name and save path for the copy of the configuration data. When you save configuration data in this manner, IIS 6.0 uses the system's machine code (Machine Key) to encrypt portions of the configuration data, so a copy of the configuration data is only useful for the machine that created the replica.

However, in the save configuration to a file dialog box, we can select the Configure encryption with password option, and then specify a password to protect the exported profile with a password. If you provide a password, IIS 6.0 replaces the machine code with a password, and you can import the configuration data to another server as soon as you provide the same password. Alternatively, we can use command-line scripting Iisback.vbs (in Systemroot/system32) to create and manage a backup copy of the IIS configuration of a remote or local computer, which an administrator can use to create a backup copy of its IIS configuration. Restore the IIS configuration from a backup copy and list and delete backup copies.

Sometimes, we just save an application pool, Web site or virtual directory configuration, instead of saving all of your configuration information, you can follow these steps: Right-click the object that you want to maintain configuration information, select Menu "All Tasks" → "save configuration to a file", as shown in Figure II, If you are preparing to import configuration data to another server, you must provide a password for the encrypted file.


screen.width-600) this.style.width=screen.width-600; "Border=0>

Figure II
If you right-click an application pool, a Web site group, or a single Web site, then choose new → application pool (from file), or "new" → "Site" → "From File", or "new" → "virtual directory (from file)", you can create a new application pool from the saved configuration file, Web site or virtual directory. Therefore, when necessary, we can only create and configure an object, using the "Save configuration to a file" feature to export objects
configuration information, and then use the "new" → "virtual directory (from files)" feature to import the configuration to more than one Web site. This means that we can first carefully configure a template and then use it to create and configure a new Web site. Of course, when a problem occurs, a copy of the configuration information can also be used to restore the site's settings.

Because the IIS 6.0 configuration information is portable, it has another benefit, which is to facilitate upgrades. Let's say that when we upgrade we cannot install Windows 2003/iis 6.0 directly on Win 2k/iis 5.0, we must change a machine, and then we will resolve the issue of how to transfer IIS 5.0 non portable configuration data to a new IIS 6.0 server. Using the portability of IIS 6.0 configuration data, the solution is to first install a new Windows 2003 server, make a full backup of the original win 2K server, and then install the second Windows 2003 server on the win 2K server to upgrade it. Export configuration data for the second Windows 2003 server (encrypted with a password), and then import the configuration data to the new Windows 2003 server. The newly installed Windows 2003 server must make some adjustments, such as allowing the IUSR account to be used, but at least now it is not necessary to perform all the configuration operations again.

The configuration data for IIS 6.0 is a standard text file (an XML file), so you can open and edit it with a text editor such as Notepad. If you modify the configuration data for IIS 5.0 or IIS 4.0, you sometimes have to restart IIS, and it may take a lot of time if you have a large number of system Web sites, such as the ISP's server. To address this problem, IIS 6.0 supports a "run-time Allow editing" feature. The run time Allow Editing feature is enabled as follows: In IIS Manager, right-click the server, select Menu Properties, and then select the Allow direct Edit metabase option, as shown in Figure three. With this feature enabled, if we open the configuration data file in Notepad, insert a configuration of a virtual directory, and then save and close the configuration file, IIS 6.0 will almost immediately be able to modify the configuration file according to the settings of the profile without restarting at all.

screen.width-600) this.style.width=screen.width-600; "Border=0>

Figure Three

Since the configuration files are allowed to be edited directly, there will inevitably be more server and application failures due to the illegal configuration files. To do this, IIS 6.0 provides a configuration file history version directory, that is,/system32/inetsrv/history, which saves a copy of the original configuration data in the directory each time you modify the configuration data or restart IIS 6.0,iis 6.0.

Current 1/4 page 1234 Next read the full text