Integration node implements non-Web-service interface to new web service
In this web service scenario, the
integration node provides compatibility with earlier versions for existing non-Web-service
clients to call a new web services implementation provided by a SOAP
toolkit.
The diagram shows
a message set being created from an interface definition (for example,
a header file) that is used by an existing client application. A WSDL
file is generated from the message set and is used to create a new
web service implementation. A message flow that uses the message set
is created to call the new web service. The message flow and message
set are deployed to an integration node, providing the original application interface
to the new web service implementation.
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 integration node 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.