Learn about a typical end-to-end scenario where you have a Web service client and you want the broker to make some existing non web-service functionality available to it.
An existing C or Cobol based system offers some business logic which can usefully be exposed as a Web service.
Like the previous example (Detail of how the broker implements a new Web service), there is some mechanism for the broker to invoke operations on the existing system (that is, the system exposes an interface to the broker). Typically, the existing system would be enabled for WebSphere® MQ, meaning that it receives MQ messages containing application data, dispatches these to the underlying implementation and then packages the return values as an WebSphere MQ response. The data structures supplied to and returned by these existing operations are defined in a C header file or Cobol copybook.
However, in this example the Web service is constrained in what it must provide because the WSDL definition for the Web services client already exists.
A possible scenario might be that a widely distributed Web services client already gives users access to a particular business capability, and the role of the broker is to offer the same interface to a new implementation that is 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.
As before, the broker can invoke the existing system function over WebSphere MQ.
To implement the scenario: