5/2/2023 0 Comments Metabase xml![]() Live Editing gets rid of this limitation. This means that all your sites and SMTP and FTP services will be down while you edit and update the configuration. The only problem with direct editing is that it requires the entire IIS process to be brought down before the file can be edited and written. You can see an example of a Metabase file, here open in Notepad, in Figure 4.1. Without making any changes from an initial installation, the only way to edit the Metabase outside of IIS Manager is to stop IIS, edit the file using a text editor, and start IIS again. Metabase Explorer, part of the IIS 6 Resource Kit, provides a more useful and friendly environment. Live editing also uses a text or XML editor, with a slight twist?we can edit the contents of the Metabase while IIS is still running. Direct editing requires the use of a simple text editor?notepad will do?or you can use a dedicated XML editor. Three primary ways exist in which we can edit the Metabase and set configuration parameters?direct editing, live editing, and Metabase Explorer. The obvious way to edit the Metabase is through IIS manager, but we already know that provides a somewhat limited range compared to the full set of available options. There are a variety of ways in which you can edit the Metabase, which I cover next. If you want to change a value in the Metabase, you will be given a location where you can find the property. ![]() Note that the Web site identifier is used, not the Web site name.Ĭontains details on individual application pools configured within the site. The settings for the first (Default) Web site. ![]() Location of all Web sites configured on the server. Location of the settings for the SMTP service. Location of the settings for the NNTP service. Location of the settings for the FTP service. Some Key Locations Within the Metabase FileĬontains details of all the MIME maps that apply to all Web sites. Some examples of additional locations within the Metabase are listed in Table 4.1. The Metabase root where all useful configuration information starts is actually /LM (short for local machine) within this are the main roots of the top-level configuration for IIS, such as configured extensions, Logging settings, the MIME map, and the root of the individual Web services. Locations within the Metabase are specified like a directory (using forward slashes), so the root of individual Web sites configured on a server is located within /LM/W3SVC. Within the Metabase file itself, the structure is tree based (as you'd expect from XML), much like the Windows registry. In fact, with the edit while running feature enabled, the version in memory is merged with the version on the disk, and the system constantly checks the disk version of the Metabase file to ensure that it's in sync with the in-memory copy. If you've enabled the edit while running feature (covered in more depth later in this chapter), this period is 60 seconds?to keep the in-memory copy in sync with the disk version. Periodically, the in-memory copy is then written to disk. When you use IIS manager to change the configuration, the internal configuration is changed first so that the rest of the IIS system has access to the changes. ![]() The Metabase is then copied into the IIS file cache for speedy access. The in-memory version of the Metabase is loaded by an IIS component called the Metabase Storage Layer, converting it to an internal, binary format. Although the Metabase schema is theoretically editable, you should only do it through the ADSI or Admin Base Objects interfaces using a C++ or C# application.Ī copy of the Metabase is also kept in memory. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |