Preface

This document describes the functionality provided by the Internet Information Services (IIS) plugin.

Refer to Deployit Reference Manual for background information on Deployit and deployment concepts.

Overview

The IIS plugin is a Deployit plugin that adds the capability to perform IIS deployments and configuration tasks.

Features

• Supports Internet Information Services version 6.0 or higher:
  • IIS 6.0 (Windows Server 2003 R2)
  • IIS 7.0 (Windows Server 2008)
  • IIS 7.5 (Windows Server 2008 R2)
  • IIS 8.0 (Windows Server 2012)
  • IIS 8.5 (Windows Server 2012 R2).
• Deploys and undeploys IIS web content.
• Creates, modifies and destroys IIS configuration elements:
  • websites
  • application pools
  • applications
  • virtual directories
• Stops and starts websites and application pools as necessary.

Upgrading from IIS plugin 3.8.1 or below

If you are upgrading from IIS plugin 3.8.1 or below to IIS plugin 3.9.0 or up, please note that the port property on the iis.Website and iis.WebsiteSpec CIs has been replaced by the iis.WebsiteBinding and iis.WebsiteBindingSpec embedded CI's that are stored underneath respectively the iis.Website and iis.WebsiteBinding CIs.

The Deployit repository is automatically upgraded the first time you start Deployit after installing IIS plugin 3.9.0. But you'll also need to make sure packages imported into Deployit include the necessary iis.WebsiteBindingSpec CIs. See the section on usage in deployment packages below for an example.

Requirements

• Deployit requirements:
  • Deployit version 3.10+
• Infrastructural requirements:
  • Administrative access to the target Windows machine is required.
  • PowerShell 2.0 must be installed on the target machine.
  • For IIS 7.0 support, the Windows PowerShell snap-in for IIS 7.0 must be installed on the target machine.

Release Notes

4.0.0

• Added support for IIS 8.5 (Windows Server 2012 R2).
• Improvements made/bugs fixed:
  • [DEPL-5468] - Error when starting/stopping an IIS application pool/website that has already been started/stopped.
  • [DEPL-5229] - Added support for secure (HTTPS) bindings.
  • [DEPL-5453] - Added support for enable32bitOnWin64 to be set on an IIS application pool(s).
  • [DEPL-5446] - Added support to sleep after creating an IIS application pool as configurable property on iis.Server.

3.9.0

• Added support for IIS 6.0 (Windows Server 2003 R2).
• Improvements made/bugs fixed:
  • Changed default of stopStartOnNoop on iis.Website and iis.ApplicationPool to true.
  • DEPLOYITPB-4237 - Changed iis.Website and iis6.website to have multiple bindings instead of just one IP/port/hostHeader combination. This change requires you to update your repository and your packages. See the section on upgrading from IIS plugin 3.8.1 or below for details.
  • DEPLOYITPB-4367 - Added stop and start steps for application pools.
  • DEPLOYITPB-4392 - Create/modify, destroy, stop and start scripts are now idempotent, i.e. they work correctly even if the state of the middleware is not exactly how they expecty it to be. Modifying a connfiguration item now only triggers the create/modify script not the destroy script so that configuration item is modified in place instead of being destroyed first.

3.8.1

• Added support for IIS 7.0 (Windows Server 2008).
• Added support for IIS 8.0 (Windows Server 2012).
• Improvements made/bugs fixed:
  • DEPLOYITPB-3947 - Added manual for IIS plugin.
  • DEPLOYITPB-4234 - Added workaround for bug in PowerShell that causes it to throw a New-Item : Index was outside the bounds of the array. error when no websites are available yet.

3.8.0

• First public release to coincide with the release of Deployit 3.8.0.
• Improvements made:
  • Added properties to allow the technical name of a configuration item to be different from the name in Deployit, e.g. websiteName on iis.Website.

3.7.1

• Fixed bug that caused IIS deployeds to be created underneath all PowerShell containers.

3.7.0

• Initial release of IIS plugin for IIS 7.5 (Windows 2008 R2).

Usage in deployment packages

The plugin works with the standard deployment package DAR format. Please see the Packaging Manual for more details about the DAR format and the ways to compose one. The following is a sample deployit-manifest.xml file that includes a few of the deployables provided by the IIS plugin:

<?xml version="1.0" encoding="UTF-8"?>
<udm.DeploymentPackage application="NerdDinner" version="2.0">
  <deployables>
    <iis.WebContent name="NerdDinner-files" file="NerdDinner-files/NerdDinner-Files">
      <targetPath>C:\inetpub\nerddinner</targetPath>
    </iis.WebContent>
    <iis.ApplicationPoolSpec name="NerdDinner-applicationPool">
      <managedRuntimeVersion>v4.0</managedRuntimeVersion>
    </iis.ApplicationPoolSpec>
    <iis.WebsiteSpec name="NerdDinner-website">
      <websiteName>NerdDinner</websiteName>
      <physicalPath>C:\inetpub\nerddinner</physicalPath>
      <applicationPoolName>NerdDinner-applicationPool</applicationPoolName>
      <bindings>
        <iis.WebsiteBindingSpec name="NerdDinner-website/88">
          <port>88</port>
        </iis.WebsiteBindingSpec>
      </bindings>
    </iis.WebsiteSpec>
  </deployables>
</udm.DeploymentPackage>

Using the deployables and deployeds

Deployable vs. Container table

The following table describes which deployable/container combinations are possible:

Deployed Actions Table

The following table describes the effect a deployed has on its container:

Extending the IIS plugin

The IIS plugin has been written upon the foundations provided by the PowerShell plugin, which is a standard part of the Deployit server distribution. Please refer to the documentation of the PowerShell plugin for details on how to extend PowerShell-based plugins.