Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This protocol operates against a site that is identified by a Uniform Resource Locator (URL) that is known by protocol clients. The protocol server endpoint is formed by appending "_vti_bin/FormsServiceProxy.asmx" to the URL of the site, for example http://www.contoso.com/Repository/_vti_bin/FormsServiceProxy.asmx.
This protocol assumes that authentication (1) has been performed by the underlying protocols.
There are also preconditions specific to this protocol that need to be met before this protocol can be used successfully.
This protocol assumes that both the protocol client and protocol server have copies of a form template (.xsn) file resource, which is addressable via a URL. This protocol does not specify how the protocol client and protocol server obtain their respective copies of this resource.
The protocol client is also expected to be processing a Universal Data Connection (.udc, .udcx) file (UDC file) that is referenced by a data adapter in a form template (.xsn) file. This protocol assumes that both the protocol client and protocol server have copies of this UDC file. This protocol assumes that this UDC file has a Type attribute on the Type element equal to "WebService" as described in [MS-UDCX] section 2.3.4. This protocol does not specify how the protocol client and protocol server obtain their respective copies of this UDC file.
This protocol assumes that the target Web service operation identified in this UDC file describes the style attribute for the soap:operation element as "document" ([WSDL], section 3.4), and the use attribute for the soap:body element as "literal" ([WSDL], section 3.5). This protocol assumes the protocol client can construct a valid request SOAP body for the target Web service operation.