4/17/2023 0 Comments Metabase logo![]() Use this table to determine where inheritance might occur. Shaded nodes are not available in IIS 5.1 or earlier versions. The following illustration shows the hierarchy of nodes in the metabase. For example, the path /LM/W3SVC/1/ROOT/Scripts/Script1.asp refers to the key that is associated with an ASP page in the virtual directory Scripts under the first virtual Web server on the local machine. ![]() The data that is contained in /LM/W3SVC/1/ServerState might be different than the data contained in /LM/W3SVC/2/ServerState, as the state can differ for each virtual server.įor each FTP or Web server, the root virtual directory is given the name ROOT. For example, ServerState is a property representing data that specifies the state of a virtual server, and, when located at the key having the path /LM/W3SVC/1/ServerState, specifies data that describes the state of the first virtual Web server on the local machine. For example, the path /LM specifies the local machine (computer) key, and the path /LM/W3SVC/3 specifies the key for the third Web site (virtual server).ĭata entries can be assigned to each key, and each data entry has a unique identifier in the metabase. Keys are identified by their path within the metabase. The keys are organized in a path structure that is similar to the Windows registry, or to a file system. Configuration data is stored in nodes (or keys) that are associated with IIS elements. The IIS metabase has a hierarchical structure. The code page that is used to store the data must be identical to the code page that is used to display the data. IIS can retrieve data from the metabase and display it using the code page that is specified by the IIS application. To support international and non-ASCII characters, the MetaBase.xml file is encoded in UTF-8 text format. IIS 6.0: The IIS metabase and schema are stored in separate XML-formatted files called Metabase.xml and MBSchema.xml. The code page used to store the data must be identical to the code page that is used to display the data. IIS can retrieve data from the metabase and display it using the code page specified by the IIS application. IIS 5.1: The IIS metabase and schema are stored as one entity in a binary-formatted file called Metabase.bin. Characters of a different code page display as garbage unless elaborate text conversion algorithms are used in an IIS application. IIS can only retrieve data from the metabase and display it using the code page of the server. IIS 4.0, IIS 5.0: The IIS metabase and schema are stored as one entity in a binary-formatted file called Metabase.bin. The internal metabase implementation is in Unicode format in order to support international and non-ASCII characters. When you start IIS, the schema and the configuration data that are contained in the metabase are read by the storage layer of IIS and loaded to the in-memory metabase from which IIS operates. The metabase changes every time IIS is configured. Data that is not related to IIS configuration should be kept outside of the metabase. Developers have the option to use ADSI to extend the schema, but it is not recommended. The schema never changes in the normal course of IIS operation. IIS follows the rules in the schema when building the configuration in the metabase. Such rules are specified in the metabase schema. For example, the GreetingMessage property, which only applies to the FTP service or an FTP site, cannot be set on a Web service or Web site. OverviewĬonfiguration information about IIS follows a set of rules, which determines things like where a property can be set. A developer can create Web sites, virtual directories, change performance and security settings, install ISAPI DLLs, and make choices about what information is written to the IIS log files, and all of that information is stored in the metabase. In IIS, the metabase stores information about the configuration of IIS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |