It is possible to call Service Broker web services from applications written in languages that have support for sockets, HTTP, and SOAP (e.g. Java, C#, and VB.NET). Details on how to create and configure this type of applications is beyond the scope of this document, since it can be done in many different ways. To understand how to use the information described here, you must be experienced in the area of web services and WSDL.
You must use the appropriate tools to convert this file to the proxy code needed to make a SOAP call. For example in a .NET environment you just have to import
servicebroker.wsdl to the Visual Studio development environment.
Use SendDocument to send the text “Test data” to the service
Service_3, version 1.
Use SendReceiveDocument to send the text “Test data” to the service
Service_3, version 1, and to receive a response from the service.
When the Service Broker receives a call, it will parse the SOAP package to make sure that it conforms to the SOAP standard. Then it starts to extract all known parameters for a given SOAP action (
SendDocument or
SendReceiveDocument). If any parameter is missing or unrecognized, the Service Broker returns a SOAP error to the client. If all parameters are present and valid, the Service Broker uses an internal protocol mapping to convert the SOAP call into an HTTP call. It then forwards the HTTP call to a service that matches the
ServiceDescription and
ServiceVersion parameters in the SOAP call.
When the StreamServer has processed the data, and returned a response to the Service Broker (
SendReceiveDocument only), the Service Broker creates a SOAP response package, and returns the processed data to the calling client.