In this Web service scenario, the broker provides a Web services interface to an existing non-web-service application. The Web service is constrained to an existing WSDL definition.
Key to symbols:
Your message flow receives a Web service request, converts it into a form expected by the existing application and invokes the existing application. The response from the existing application is converted into a valid Web service response.
In this example, an existing HTTP Web service client provides information on a given subject (stock prices or exchange rates, for example). You want to replace this service with an inhouse database lookup solution, but want to make no changes to the clients since these are widely deployed.
In this example, an existing, C or Cobol based, system can usefully be exposed as a Web service. There is also a constraint on what the Web service must look like – we already have the WSDL definition for a widely distributed Web services client which gives your users access to a particular business capability. The role of the broker will be to offer the same interface to a new implementation based on the existing system. Perhaps the original Web services provider offers a different quality of service or is to be discontinued for some reason.
(See Importing from WSDL).
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac34550_ |