Note that WSO2 EI is shipped with the following changes to what is mentioned in this documentation:
repository/samples/directory that includes all Integration profile samples is changed to
repository/samples/resources/directory that includes all artifacts related to the Integration profile samples is changed to
Objective: Demonstrate receiving SOAP messages over TCP and forwarding them over HTTP
- Configure ESB to use the TCP transport and configure sample Axis2 client to send TCP requests. See here for details on how to do this.
- Start Synpase using sample 266: ie synapse -sample 266
- Start Axis2 server with SimpleStockService deployed
This sample is similar to Sample 250 . Only difference is instead of the JMS transport we will be using the TCP transport to receive messages. TCP is not an application layer protocol. Hence there are no application level headers available in the requests. ESB has to simply read the XML content coming through the socket and dispatch it to the right proxy service based on the information available in the message payload itself. The TCP transport is capable of dispatching requests based on addressing headers or the first element in the SOAP body. In this sample, we will get the sample client to send WS-Addressing headers in the request. Therefore the dispatching will take place based on the addressing header values.
Invoke the stockquote client using the following command. Note the TCP URL in the command.
The TCP transport will receive the message and hand it over to the mediation engine. Synapse will dispatch the request to the StockQuoteProxy service based on the addressing header values.
The sample Axis2 server console will print a message indicating that it has received the request: