Logical Server Information in Deployment Reports

In the XML deployment report, the <LogicalServers> element contains information about the logical servers to which you need to deploy applications. You need this information to validate configuration of the corresponding physical servers at deployment. The <LogicalServers> element also contains information about settings, resources, and endpoints associated with each logical server. For more information, see Overview of Key Sections in Deployment Reports.

The <LogicalServers> element contains one or more <LogicalServer> elements that identify each logical server in the deployment report. If these logical servers exist within zones, the <LogicalServers> element also contains a <Zone> element for each of these zones. A zone defines communication boundaries, physical or otherwise, in a logical datacenter. For more information, see Binding Information in Deployment Reports.

The following sections contain more information about the <LogicalServer> element:

• Logical Server Information in the <LogicalServer> Element

• IIS Metabase Settings for IIS Web Servers

• Information about Logical Server Connections

Logical Server Information in the &lt;LogicalServer&gt; Element

The following example contains a <LogicalServer> element for an Internet Information Services (IIS) Web server. The "Extends" attribute "Microsoft_WebHost:WebServer" identifies the IIS Web server:

<LogicalServer Name="MyWebServer" Definition="MyLogicalDatacenter:MyLogicalDatacenter.MyWebServer" Extends="Microsoft_WebHost:WebServer" InstanceId="f156c631-2fc4-46d2-b52d-a84ba52a61dc">
   ...
</LogicalServer>

Within this element, you can find the following information:

• Settings configuration expected on logical servers for deployment.

• Connection information for logical servers and zones.

The logical server type determines the type of information included in the deployment report. For example, the <LogicalServer> element for IIS Web servers and Windows client servers contains two <Resource> elements, "OperatingSystemDescription" and "CommonLanguageRuntime." You can define launch conditions that control application installation on the target computers using this information.

The following sections contain more information about these resources:

• "OperatingSystemDescription"

  This element contains <Setting> elements that include operating system settings expected on the logical server.

  The following example contains an "OperatingSystemDescription" element that includes the types of operating system information for an IIS Web server:

  <Resource Name="OperatingSystemDescription" Definition="MyLogicalDatacenter:MyLogicalDatacenter.MyWebServer.OperatingSystemDescription" Extends="Microsoft_OperatingSystem:OperatingSystemDescription" InstanceId="ac4ab192-87f3-410f-9729-c25e3738ff9f">
     <Setting Name="Suite" Definition="Microsoft_OperatingSystem:SuiteOptions" State="Set">
     ...
     <Setting Name="BuildNumber" Definition="System:Int" State="Set">
     ...
     <Setting Name="OsType" Definition="Microsoft_OperatingSystem:OsType" State="Set">
     ...
     <Setting Name="ProductType" Definition="Microsoft_OperatingSystem:ProductType" State="Set">
     ...
     <Setting Name="ServicePack" Definition="Microsoft_OperatingSystem:ServicePack" State="Set">
  </Resource>
  

• "CommonLanguageRuntime"

  This element contains a <Setting> element named "Version." This <Setting> element contains the common language runtime (CLR) version on the logical server.

  The following example shows a "CommonLanguageRuntime" element with a "Version" element containing version 2.0.0.0 of the common language runtime:

  <Resource Name="CommonLanguageRuntime" Definition="MyLogicalDatacenter:MyLogicalDatacenter.MyWebServer.CommonLanguageRuntime" Extends="Microsoft_CommonLanguageRuntime:CommonLanguageRuntime" InstanceId="983a6ce7-8963-4c02-9e1f-7fc5dea42757">
     <Setting Name="Version" Definition="System:Version" State="Set"> 
         <Value>2.0.0.0</Value> 
     </Setting>
     <Resource Name="GlobalAssemblyCache" Definition="MyLogicalDatacenter:MyLogicalDatacenter.MyWebServer.CommonLanguageRuntime.GlobalAssemblyCache" Extends="Microsoft_CommonLanguageRuntime:GlobalAssemblyCache" InstanceId="88d5bb77-3a3f-450e-8f89-c7c4934dfe2e" />
  </Resource>
  

IIS Metabase Settings for IIS Web Servers

For an IIS Web server, the <LogicalServer> element contains a <Resource> element named "InternetInformationServices." This <Resource> element contains <Setting> elements and <Resource> elements that identify the IIS metabase settings expected in the deployment environment. You need to validate that these settings match those configured on the target servers. However, some of these setting names, values, and types differ from their IIS counterparts and require translation. For more information, see the following topics:

• How to: Find IIS Metabase Settings for IIS Web Servers in Deployment Reports

• Setting Names that Differ from the IIS Metabase

• Setting Types that Differ from the IIS Metabase

Information about Logical Server Connections

The <LogicalServer> or <Zone> element contains an <Endpoint> element for each endpoint on the logical server or zone. An <Endpoint> element contains a <Setting> element named "ConnectedToEndpoints" when an endpoint connects to another endpoint. You can use the "ConnectedToEndpoints" element to identify all the endpoints connected to that endpoint. The "ConnectedToEndpoints" element contains a Globally Unique Identifier (GUID) that matches the "InstanceId" attribute for the connected endpoint. Other <Setting> elements in the <Endpoint> element contain information about the endpoint's settings.

In addition, you need to create a Web site on the target computer or use an existing Web site on the same computer for each Web site endpoint on an IIS Web server.

The following list contains the required settings if you choose to create a Web site:

• You need to specify the server bindings, such as the IP address if it is different from the default, the port number, and the host header, if required, by configuring the ServerBindings setting on the Web site endpoint. You can perform this task on the logical datacenter diagram.

• If you need to enable secure ports (HTTPS), you need to configure the SecureBindings setting on the Web site endpoint.

• You need to specify a physical directory on the target computer for each Web site.

If you choose an existing Web site, make sure that you are deploying to the correct location by confirming that the ServerComment setting matches the Web site description in IIS.

For ASP.NET applications running on IIS 6.0 or later, the deployment report does not indicate to which Web site application pool an application is bound. To include this information in the deployment report, add a custom setting referencing the application pool to the ASP.NET application.

See Also

Concepts

Overview of Deployment Using Deployment Reports