Clear instructions. Easy to follow. No jargon. Pictures helped. Didn't match my screen. Incorrect instructions. Too technical. Not enough information. Not enough pictures. Any additional feedback? Submit feedback. Thank you for your feedback! The centralized configuration store of the previous IIS releases, known affectionately as the metabase, is gone. This hierarchy is comprised of a global applicationHost. These are the same web. NET application framework to store application settings in a portable way.
Here's an example:. In the past, IIS application settings had to be explicitly configured in the machine-level metabase repository before the application could function correctly.
With distributed web. This dramatically simplifies deployment, allowing self-contained applications to be simply copied to the target server's application directory and thus be up and running immediately with the desired settings. The new configuration system also gives comprehensive control to the server administrators, allowing them to delegate certain configuration options to the application while maintaining control over others for security or business reasons.
In this way, applications on hosted servers can set essential configuration directly in their application without requiring the calling of the server administrator for help or using an external configuration panel. In the true spirit of IIS 7. New modules can add their own configuration schema, enabling applications to configure their features side-by-side with the IIS and ASP. NET configuration:. The custom configuration sections use the same configuration schema as the configuration for the IIS 7.
It does this by providing a compatibility layer that emulates the ABO APIs, on top of which all other legacy configuration APIs are based, allowing such scripts to read and change configuration just like they did in the previous releases of IIS. For more information about metabase compatibility, see the "Improved Performance" and "Backward Compatibility" sections towards the end of this article.
While the new structured XML configuration format makes it easier to work with configuration in your favorite text editor, IIS also provides a host of management tools and APIs for administrators to simplify server management and enable automated configuration and deployment.
What's more, the tool enables delegated management, letting application owners manage their applications remotely without having administrative access to the server computer.
Armed with this capability, users of hosted services can run the administration tool on their home desktop and connect remotely to manage their applications on the hosted server.
Server administrators, of course, have complete control over what management features are delegated to application owners. Finally, the Administration tool is completely extensible, building on top of configuration system extensibility to allow custom management UI to be added to the tool.
You can learn more about the IIS Manager tool and how to add your own administration plug-ins at iis. For more flexible command-line administration, IIS 7. This tool provides a comprehensive set of management functionality and better support for bulk operations than the UI. This powerful utility makes it easy to read and write configuration, access site and application pool state information, and perform almost any other management task, all from the command prompt.
With appcmd. You can start and stop sites, recycle application pools, list running worker processes, examine currently executing requests, and search Failed Event Request Buffering FREB trace logs. NET configuration data. The tool is built to allow flexible searches for supported server objects, for example, letting you quickly find sites with a particular setting set or application pools that are stopped.
When performing a search, you can use any number of conditions on any of the object's properties, including using numeric ranges and simple wildcard string matching. For example, you can find and recycle all application pools that host applications for a certain site in a single command.
In addition to the manual server administration with IIS Manager or the appcmd. First, you can utilize the Microsoft. Administration API to manage the server from. NET applications. Administration, the new. NET Administration API, makes it easy for managed code applications to programmatically provision IIS sites and applications, access important state and diagnostic information, and otherwise configure the server.
NET Framework-based applications to easily access IIS configuration and state information opens up a world of possibilities for writing.
NET pages. As an example, Figure 4 shows a small C program that uses Microsoft. Administration to create a new Web site from the command line. Administration makes IIS operations and configuration tasks a breeze, right inside your application in a. NET-compliant language of your choice. It also makes it easy to access runtime state information about the server, such as the running worker processes or currently executing requests.
The Microsoft. Administration API serves as the foundation for accessing custom configuration inside custom. For an example of an end-to-end server package, including an image copyright handler to enhance the Web server and associated configuration and management components, take a look at iis.
In the Windows Server "Longhorn" timeframe, the IIS team is creating a unified extensibility model for adding custom management objects or extending existing ones, which will enable custom management functionality to be automatically exposed through the different management features including scripting and the Microsoft.
Administration API. While you cannot add or extend management objects in Windows Vista, you can use Microsoft. Administration and other APIs to access and manipulate your custom configuration sections just like you can do with existing IIS configuration sections.
How is this possible? First, the new API features a type-safe, well-encapsulated object model. Development is much easier with the new server object model, which provides specialized interfaces for all of the basic server objects and tasks. This includes:. These classes expose a much greater set of the server's functionality than before more than needed to build all of the features that ship with IIS , but are also much easier to use then the loosely typed ISAPI interfaces.
Developers will also benefit from improved patterns for memory and state management. Most of the IIS 7. The new API also simplifies many complex request processing tasks, such as response buffering, authentication, and preparing response data for the client. A few months ago, I started a series of posts of my blog that explain the critical improvements and patterns in the new programming model. NET 1. But don't be fooled-while the familiar ASP.
In IIS 7. NET comes in two versions: Classic mode and Integrated mode. Classic mode works exactly the same way as it did in previous versions of IIS. Integrated mode, the new platform default, uses a brand new engine to provide unparalleled integration with the IIS Web server. In Integrated mode, ASP. This is basically the best of both worlds-the familiar interfaces and convenience of the. NET 2. In addition to being able to write new ASP.
NET modules can be made a lot more powerful just by changing a few configuration options in your web. With this installation, you have everything required to use IIS 7. By default, request filtering in IIS 7. To change these defaults add the following XML to your App. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Configuring Internet Information Services 7. Is this page helpful?
Please rate your experience Yes No. Any additional feedback? In this article.
0コメント