Working with Transports

A transport is responsible for carrying messages that are in a specific format. The ESB Profile of WSO2 Enterprise Integrator supports all the widely used transports including HTTP/s, JMS, and VFS, and domain-specific transports like FIX. All ESB transports are directly or indirectly based on the Apache Axis2 transports framework. This framework provides two main interfaces that each transport implementation must implement.

• org.apache.axis2.transport.TransportListener - Implementations of this interface specify how incoming messages are received and processed before handing them over to the Axis2 engine for further processing.
• org.apache.axis2.transport.TransportSender - Implementations of this interface specify how a message can be sent out from the Axis2 engine.

Because each transport implementation has to implement the above two interfaces, each transport generally contains a transport receiver/listener implementation and a transport sender implementation. You configure, enable, and manage transport listeners and senders independently of each other. For example, you could enable just the JMS transport sender without having to enable the JMS transport listener.

For more information on transports, see the following topics:

• Configuring Transports
• ESB Transports

For information on configuring transport-level security, see Configuring Transport Level Security in the WSO2 Administration Guide.