About the Web Service Host sample
The Web Service Host sample shows you can invoke a legacy application as a web service.
In this sample, the supplied legacy application is invoked by sending a WebSphere MQ message
to a queue. The format of this message is mapped to a C header file.
The sample comprises two message flow paths, implemented in a single message flow. The message flow is designed so that multiple
instances of the Web service can run concurrently. This is achieved by storing the HTTP context (reply identifier) in a "state" queue
along with the correlation identifier of the message sent to the legacy application.
- Path 1:
- A SOAP message is received via HTTP.
- The SOAP message transforms data from the SOAP body to a legacy message.
- The legacy message is output to a WebSphere MQ queue to invoke the legacy application.
- The http context is built into a second message, correlated to the message just sent to the legacy application.
- This state message is sent to a WebSphere MQ queue for later retrieval (see Path 2).
- Path 2:
- A reply is received from the legacy application via WebSphere MQ.
- A state message is retrieved from a WebSphere MQ queue.
- The legacy message data is incorporated into a SOAP message body.
- The http context is set from the state message.
- The SOAP response message is sent via HTTP.
Back to sample home