ESB Lessons for Beginners

when request message comes from client to the ESB as we know initially it hits the transport so when we go deep into the transport there we know there are two interfaces implemented namely TransportListener and TransportSender. So TransportListener is responsible to receive and process the client request and TransportSender is responsible for process and send response back to the client.wso2 ESB support no of transport in order to do establish better communication between client and the back-end service One of the Two Transports Supported wso2 ESB are HTTP Pass Through Transport HTTP NIO Transport In Wso2 ESB 5.0.0 the default transport is HTTP Pass Through the reason is when comparing HTTP Pass Through Transport and HTTP NIO Transport, HTTP Pass Through provided high performence. So why to use HTTP Pass Through Transport over HTTP NIO Transport? 1.What is happen when we use HTTP NIO Transport ? In HTTP NIO Transport the transport listener is...

When there are 2 applications runs on different platforms and when they need to communicate each other there should be a way to do that in order to support to their communication, as an example when client operate in J SON format and server operate in XML format there should be someone in the middle to translate client request to a format understand by the Server and on the other way Server response should be understand by the client. That is the place where ES B come in to the picture. The client can send the message to ESB in JSON format and ESB convert the JSON message to SOAP format and do the processing and then SOAP message converts to XML format which is understand by the Server. When we go deep in to the picture then we can see there are several components in ESB which supports to the communication. The verticle components where the message is go through are Transport Message builder and formatter QoS Mediation engine   ...