Share via

How to: Find Web Service and Web Content Absolute URIs in Deployment Reports

  • Article

When you prepare to deploy Web service or Web content consumer applications, you need to update their configuration files with the locations of the Web services or Web content in the deployment environment. You can retrieve the absolute URIs of Web service or Web content provider endpoints from the XML version of the deployment report. For more information, see Application Information in Deployment Reports.

To retrieve the absolute URI of a Web service or Web content provider endpoint

  1. Open the XML deployment report.

  2. Under the <Applications> element, locate the <Application> element for the connected ASP.NET application.

  3. Under the <Application> element, locate the <Endpoint> element for the Web service or Web content provider endpoint.

  4. Under the <Endpoint> element, locate the "Uri" <Setting> element.

  5. Under the "Uri" <Setting> element, locate the "Absolute" <Facet> element and retrieve the URI specified by its <Value> element.

    Note

    If the "Absolute" element does not contain a value, set the Service URL setting for the Web service provider endpoint or the Relative Path setting for the Web content provider endpoint on the application diagram. On the logical datacenter diagram, set the URL setting for the Web site endpoint to which the Web service or Web content provider endpoint is bound on the deployment diagram. To view and edit settings for a Web service or Web content provider endpoint, select the endpoint on the application diagram and view the Application Endpoint Settings node in the Settings and Constraints Editor. To view settings for a Web site endpoint, select the endpoint on the logical datacenter diagram and view the Logical Server Endpoint Settings node in the Settings and Constraints Editor. For more information, see Settings and Constraints Editor.

Once you have retrieved all the absolute URIs for the Web service or Web content provider endpoints, you can update the URIs for the consumer applications. For more information, see How to: Update Web Service Client URIs in Configuration Files.

Note

The "Absolute" <Facet> element might differ from the ServerBindings or SecureBindings setting on the IIS Web server with the Web site endpoint that hosts a Web service. To view either setting, select the IIS Web server on the logical datacenter diagram and search for the setting under Logical Server Settings in the Settings and Constraints Editor. However, there is no constraint that identifies this difference as a conflict during validation of the deployment diagram. Therefore, make sure that your deployment process confirms that the value of these settings and the "Absolute" <Facet> value are identical. Otherwise, the consumer endpoints will not be able to consume the deployed Web services.

Example

The following example contains an <Endpoint> element for a Web service provider endpoint named "MyWebService". Under this element, the "Uri" <Setting> element contains <Facet> elements that describe the absolute URI of the Web service. The "Absolute" <Facet> element contains the absolute URI for the Web service provider endpoint.

<Endpoint Name="MyWebService" Definition="MyWebService:MyWebService.WebService1" Extends="Microsoft_Web:WebService" InstanceId="f8c1de34-1534-4dbe-b406-e0e8cfd388f2">
   ...
   <Setting Name="Uri" Definition="Microsoft_Web:Uri">
      <Facet Name="Relative" Definition="Microsoft_Web:Uri" State="Set">
         <Value>MyWebService/MyWebService.asmx</Value>
      </Facet>
      <Facet Name="Base" Definition="Microsoft_Web:Uri" State="Set">
         <Value>http://www.mydomain.org/</Value>
      </Facet>
      <Facet Name="Absolute" Definition="Microsoft_Web:Uri" State="Set"> 
         <Value>http://www.mydomain.org/MyWebService/MyWebService.asmx</Value> 
      </Facet>
   </Setting>
</Endpoint>

See Also

Concepts

Overview of Deployment Using Deployment Reports

Reference

Overview of Key Sections in Deployment Reports