Binding Information in Deployment Reports
In the XML deployment report, the <Binding> element contains information about the binding (hosting) relationships between applications and the logical servers to which they need to deploy. Using this information, you can to configure application settings that depend on physical binding information between logical servers and their physical hosts. For more information, see Overview of Key Sections in Deployment Reports.
Tip
Binding relationships are defined on the deployment diagram used to generate the deployment report. Binding an application to a logical server defines a hosting relationship between that logical server and the application. Therefore, the logical server with a bound application should have the same configuration as the physical server(s) to which that application needs to deploy. For more information, see Overview of Deployment Using Deployment Reports.
The <Binding> element contains two elements: <BoundLogicalServer> and <Zone>. In addition, the <BoundLogicalServer> element is included only if a logical server has at least one application bound to it. The <Zone> element is included only if a zone contains at least one bound logical server.
The following sections contain more information about these elements:
Information about Bound Logical Servers
Information about Zones
Information about Bound Logical Servers
The <BoundLogicalServer> element identifies each logical server that is bound with one or more applications. The following example contains a <BoundLogicalServer> element for a Windows client server. The "Extends" attribute containing "Microsoft_WindowsHost:WindowsHost" identifies the Windows client server:
<BoundLogicalServer Name="MyWinServer" Definition="MyLogicalDatacenter:MyLogicalDatacenter.MyWinServer" Extends="Microsoft_WindowsHost:WindowsHost">
...
</BoundLogicalServer>
A <BoundLogicalServer> element contains an <Application> element for each application bound to that logical server. This <Application> element has a "HostedOn" attribute. This attribute also identifies the logical server to which the application is bound.
Note
This <Application> element references the same <Application> element that appears under the <Applications> element. For more information, see Application Information in Deployment Reports.
In addition, the <Endpoint> element for each application endpoint under an <Application> element has a "HostedOn" attribute. This attribute identifies the logical server endpoint to which the application endpoint is bound.
Note
In Distributed System Designers, Web service and Web content provider endpoints can be bound to different Web site endpoints. Therefore, your deployment process should make sure that a Web service or Web content provider endpoint is deployed only to a single Web site endpoint.
The following example contains a <BoundLogicalServer> element for a Windows client server. The "Extends" attribute "Microsoft_WindowsHost:WindowsHost" identifies the server type. This server hosts a Windows application that consumes a Web service. Therefore, this element contains an <Application> element that has an "Extends" attribute of "Microsoft_WindowsApplication:WindowsApplication." This element also has a "HostedOn" attribute that names the logical server that should host the application.
The <Application> element also contains an <Endpoint> element with an "Extends" attribute of "Microsoft_Web:WebServiceClient." The <Endpoint> element has a "HostedOn" attribute that names the logical server endpoint that should host the Web service consumer endpoint.
<BoundLogicalServer Name="MyWinServer" Definition=" MyLogicalDatacenter:MyLogicalDatacenter.MyWinServer" Extends="Microsoft_WindowsHost:WindowsHost">
<Application Name="MyWinApp" Definition="MyWinApp:MyWinApp" Extends="Microsoft_WindowsApplication:WindowsApplication" InstanceId=" eb6c518d-59a4-45c5-ac9d-fe51796c285d" HostedOn="/*[InstanceName="SimulationRoot"]/SimulationHost[InstanceName="MyLogicalDatacenter"]/MyZone/MyWinServer">
...
<Endpoint Name="WebServiceConsumer" Definition="MyWinApp:MyWinApp.WebServiceConsumer1" Extends="Microsoft_Web:WebServiceClient" InstanceId="c3286e12-6fde-43b6-b08f-139391813df1" HostedOn="/*[InstanceName="SimulationRoot"]/SimulationHost[InstanceName="MyLogicalDatacenter"]/MyZone/MyWinServer/MyHTTPClientEndpoint" />
...</Application>
</BoundLogicalServer>
Information about Zones
A <Zone> element is included if one or more bound logical servers exist within a zone. The <BoundLogicalServer> elements for those logical servers then appear in that <Zone> element. If a zone contains one or more zones that contain bound logical servers, <Zone> elements for those inner zones appear within the <Zone> element of the outer zone.
The following example contains a <Zone> element for a zone containing a bound logical server. This zone also contains another zone that contains a bound logical server:
<Zone Name="Zone1" InstanceId="19623ac0-9f85-48c6-9c1e-b8483c3fb5d9">
...
<Zone Name="Zone2" InstanceId="34b2ff25-4df1-46b7-ba4e-95adc22a3d23">
...
<BoundLogicalServer Name="MyWebServer" Definition="MyLogicalDatacenter:MyLogicalDatacenter.MyWebServer" Extends="Microsoft_WebHost:WebServer">
...
</Zone>
<BoundLogicalServer Name="MyWinServer" Definition="MyLogicalDatacenter:MyLogicalDatacenter.MyWinServer" Extends="Microsoft_WindowsHost:WindowsHost">
...
</Zone>
Endpoints on a zone are identified with <Endpoint> elements in a <Zone> element. If a zone endpoint connects to a logical server endpoint, the <Endpoint> element contains an <Endpoint> element for that logical server endpoint.
The following example contains <Endpoint> elements that identify a zone endpoint that is connected to a logical server endpoint:
<Endpoint Name="ZoneEndpoint1" Definition="MyLogicalDatacenter:MyLogicalDatacenter.Zone1.ZonePort1" Extends="Microsoft_Datacenter:ZoneEndpoint" InstanceId="7494e5c8-cf33-4460-a86b-88fb9ed80c90">
<Endpoint Name="WebSiteEndpoint1" Definition="MyLogicalDatacenter:MyLogicalDatacenter.MyWebServer1.HttpServer1" Extends="Microsoft_Web:HttpServer" InstanceId="48e9c446-6e1f-406f-ba3b-988c344348f8" />
...
</Endpoint>