See information about the latest product version
Broker implements non-Web-service interface to new Web service
In this Web service scenario, the broker provides compatibility with earlier versions for existing non-Web-service clients to call a new Web services implementation provided by a SOAP toolkit.

Key to symbols:
Possible uses
You want to migrate an application to a Web service implementation, for example an EJB implementation hosted by an application server to offer better scalability.
However, a significant number of your users have existing clients that cannot be immediately replaced. Existing clients can use the broker to use the new Web service implementation.
Design steps
- Create a message set for the business messages, for example, by importing an existing interface definition such as a C header file or COBOL copybook.
- Generate a WSDL definition from the message set.
- Use a SOAP toolkit or application server to create a suitable Web services implementation based on the WSDL.
- Develop a message flow to mediate between the original existing client and the new Web service.
At run time
Your message flow receives a request from the existing client, converts it into a Web services request and invokes the Web service. The response from the Web service is converted into a form understood by the existing client.