Changes in IIS 7.0

All points categorized in to four major sections: Architecture, Management, Compatibility and Troubleshooting. 

Architecture

  • Request processing, PHP support, and the configuration store approach changed
  • Modular approach - all features become building blocks and giving end user to customize the server based upon their need –removing unnecessary load and eliminating the components updates/patch that are not used.
  • Here are some default modules that installs while installing IIS, below are bare minimum modules.
    • Common HTTP features - Static Content, Default Document, Directory Browsing, and HTTP errors
    • Health and Diagnostics features - HTTP Logging, Request Monitor
    • Security features - Request Filtering
    • Performance features - Content Compression
    • Management Tools - IIS Management Console
    • Windows Process Activation Service
  • All modules can be plug into the integrated pipeline
    • Integrated Request Pipeline
    • It’s is set of steps that occurs for every request on server
    • It gives flexibility to run multiple application framework like form authentication and logging over PHP content 
    • Any site which has Integrated pipeline runs into either of this mode
      • Integrated
        • Allows custom code to get plugged into the pipeline and giving control over the request process
      • Classic
        • Reproduces IIS 6.0/ISAPI functionality through an ISAPI module 
  • Modular design resulting less component and memory footprint on server
  • Each component works independently in pipeline – end user can tailor the server and have customized IIS
  • Custom developed module can be attached if any gap in pipeline, no need to wait for next patch or releases from Microsoft.
  • Ability to overwrite the default modules with custom code.
  • Flexible XML based configuration approach on place of cumbersome XML.
  • New configuration system is now machine-independent, can be now easily port to other servers 
  • IIS 7.0 shared configuration features for the Web farms environment; master .config can be shared to all nodes of web farm environment and can be exported, password protected config file, easy to deploy from pre-production to production server.
    • All configuration broken into two categories
      • applicationhost.config // server-wide settings
      • web.config // site specific settings

Management Console


  • UI console completely revamped
  • UI has task oriented approach
  • IIS all features and their properties grouped by category like security, admin, modules, handlers etc.
  • New command line tool(APPCMD.exe) released for the people who love to manage by command(basic operations)
  • Microsoft.Web.Administration and a new Windows Management Instrumentation (WMI) provider added to expose APIs for developers.
  • User has same UI experience as he/she experience locally while managing remote server 
  • Firewall complaint (communication happens on HTTPS)
  • In same console you can add multiple remote desktop or site
  • IT administrators have the ability to delegate administration tasks to non-admins.
  • Delegated Administration is essentially remote administration with limited access on individual sites or Web applications.
  • For example, if you do not want to allow user to change the authentication type for particular site, you can set that feature.




Backward Compatibility


  • IIS 6.0 metabase compatibility and IIS 6.0 management console — need to be install for IIS 6 compatibility 
  • ADOMapper components(IIS 6.0 Admin Based Object (ABO) and ADSI (Active Directory Services Interface) that handles all configuration compatibility concern in IIS7 for IIS 6.0
  • It cannot read or write IIS 7.0 properties
  • Just allow to meta based script to run on top of new config system



Troubleshooting


  • Failed Request Tracing added to help in troubleshooting. It is helpful in many situations, especially when request hangs or produces errors.
  • Log is just XML file, clean and easy to read – not installed by default.


If any major point missing here and you think it should be here, I would appreciate if you put that into comment sections.




Comments

Popular posts from this blog

Difference between Parse/TryParse/ParseExact/TryParseExact

Benefits of Test Driven Development (TDD)

Version history of C#