Web services

StreamServer services that are registered in a Service Broker can be exposed via web services through the SOAP protocol. A client that needs to invoke these services can import the Service Broker WSDL description and use this information to create the necessary infrastructure.

The exposed web services are not the same as the services published in the Service Broker. The Service Broker acts as a SOAP gateway that exposes two web services: SendDocument and SendReceiveDocument. Both web services accept the following parameters:

•	ServiceDescription – The name of the published service.

•	ServiceVersion – The version of the published service.

•	ServerID – The server ID of a specific StreamServer.

•	DocData – The data to send to the service.

Example 2

Client application calling a SendDocument web service

The client makes the SOAP call SendDocument("Service_3", "", "", soapRequestData), and the Service Broker invokes the service Service_3 in the appropriate StreamServer instance.

The StreamServer processes the soapRequestData, and sends the output to a printer.

 

 

 

Example 3

Client application calling a SendReceiveDocument web service

The client makes the SOAP call SendReceiveDocument("Service_3", "", "", soapRequestResponseData), and the Service Broker invokes the service Service_3 in the appropriate StreamServer instance.

The StreamServer processes the soapRequestResponseData, and sends the output in the response to the client.