The target system has IIS 7 and the IIS Metabase and IIS 6 Configuration Compatibility feature is installed. The target system has IIS 6 or earlier. Release and debug versions of the DLL file, as well as the Visual Studio 2008 C++ project that was used to create the file, are installed to the following location. Windows 2008 x64 R2 (IIS 7.5) > ColdFusion 9 Enterprise (Multiserver JRun Install). My problem: It appears I must enable the 'IIS 6 Metabase Compatibility' option in order to connect IIS websites to CF Instances in the Web Server Configuration Tool (if I disable it no IIS websites appear in the select list). Metabase Compatibility with IIS 7 and Above • • 6 minutes to read • Contributors • • In this article by Introduction The configuration system in IIS 7 and above is compatible with legacy configuration interfaces at the API level. It supports the Admin Base Objects (ABO) interface, also known as IMSAdminBase, as well as the ADSI and WMI providers that were built on top of ABO in IIS 6.0. Existing applications and scripts can still call into those programmatic interfaces on IIS 7.0 and above and continue to work, as long as the Metabase Compatibility component of IIS is installed. Note By default, this component is not installed. Installing Metabase Compatibility Support You can find this component in setup under Internet Information Services->Web Management Tools -> IIS 6.0 Management Capability Feature. This component is not installed by default because IIS is not initially set up to use it. The legacy interfaces have some limitations and are not ideal for working with distributed configuration files (see Limitations section below); therefore it is recommended that over time, and especially when opening up the configuration system for more and more delegation (i.e. More and more web. Best armor in dragonfable. config files with IIS settings in them are present on the system), customers will consider porting legacy scripts and applications over to the new system and its interfaces. It is also recommended that new scripts and applications be developed using the new interfaces, so they work ideally with the new system, and can have access to the new properties, concepts and structure of the configuration system. When all of the legacy scripts and applications are ported to the new interfaces, it is recommended to uninstall the Metabase Compatibility feature. How Metabase Compatability Works The Metabase Compatibility feature runs inside the Metabase service (IISADMIN). It intercepts all method calls to ABO. If the information in the method call is related to the web server configuration, it is mapped to the new system. If it is related to FTP, or SMTP, or NNTP configuration, then it follows the regular logic of the Metabase system and ends up in the Metabase file. Note that even custom properties that are under the web server configuration are mapped to (and persisted in) the new system. The mapping decision is based on the Metabase node in question. Web server configuration is typically under LM/W3SVC, including custom properties, with some few additions like Mime Maps. Mapping is done to translate back and forth between the ABO view back and the new system view. For example, the new system has a concept of applications, under each site and above all virtual directories. The legacy system handles applications differently: they are simply virtual directories with a special property to mark them as applications (AppIsolated, or AppRoot). When calling ABO to write web server configuration, the Metabase Compatibility component will persist the data in applicationHost.config. This is referred to as 'write-through', because the information is not kept in-memory. When calling ABO to read web server configuration, the Metabase Compatibility component will read it from applicationHost.config. This is referred to as 'read-through', because the information is again not fetched from memory. Incomplete data that is not ready for consumption by the server runtime is persisted into a special section in applicationHost.config, called customMetadata. This section is used as a persistent store for the Metabase Compatibility feature, and customers should never modify its content. An example of incomplete data is when the legacy script set the site id but not the site bindings. In IIS 6.0, such a call would have created an invalid site object in configuration. In IIS 7.0 and above, it is kept in the section, which is not consumed by the server. If a subsequent call is made to set the site bindings, then the site object is considered complete, and persisted in its entirety to the section, where it will be picked up by the server runtime. Temporary data will be removed from at that point, so the user will not need to cleanup leftovers from the system. Jetclean pro 1 2 0 118 portable sawmill. Powerful Engine Advanced technology cleans registries, Windows, apps, shortcuts, RAM and eliminates other debris that can bog down your PC. Unrivaled Functionality only utility cleaner to provide RAM Clean, Uninstaller, Registry Defrag, and Internet booster.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |