Available Transports
Following is a list of known transports (also called "providers") for Mule. Some functionality is contained within modules instead of transports—see Modules Reference. For more information on transports, see the following topics:
The following list includes prominent transports. Transports that are available only in Mule Enterprise are denoted by Enterprise.
Note that in Mule 3, CXF and Jersey are no longer classed as transports. They are now modules that use an underlying transport (for instance HTTP or HTTPS) to communicate between client and service.
Mule Transports
| Transport | Description |
|---|---|
The Mule AJAX connector allows Mule events to be sent and received asynchronously to and from the web browser |
|
Allows EJB invocations to be made using outbound endpoints. |
|
This transport supplies various email connectivity options. |
|
This transport allows files to be read and written to directories on the local file system. The connector can be configured to filter the file it reads and the way files are written, such as whether binary output is used or the file is appended to. |
|
Allows files to be read from or written to a remote FTP server. |
|
This transport supplies HTTP transport of Mule messages between applications and other Mule servers. |
|
A secure version of the HTTP transport. |
|
Connectivity to IMAP mail folders. |
|
A secure version of the IMAP transport. |
|
JDBC Transport |
A transport for JDBC connectivity. Some of its features are available only in Mule Enterprise. |
Provides support for exposing services over HTTP by embedding a light-weight Jetty server. For inbound endpoints only. |
|
A secure version of the Jetty transport. |
|
A Mule transport for JMS connectivity. Mule itself is not a JMS server but can use the services of any JMS 1.1 or 1.02b compliant server such as ActiveMQ and OpenJms, and commercial vendors such as Weblogic, SonicMQ, and more. |
|
Allows you to send and receive Mule Messages to/from an LDAP directory. Now handled by the LDAP Connector. |
|
Connectivity to POP3 inboxes. |
|
A secure version of the POP3 transport. |
|
Provides scheduling facilities with cron / interval definitions and allows Mule events to be scheduled/rescheduled. |
|
Enables events to be sent and received over RMI via JRMP. |
|
Provides facilities for Mule components to listen for events received via a servlet request. There is also a servlet implementation that uses the Servlet transport to enable REST style services access. This transport is now bundled with the HTTP transport. |
|
Connectivity to SMTP servers. |
|
A secure version of the SMTP transport. |
|
Provides secure socket-based communication using SSL or TLS. |
|
This transport provides connectivity to streams such as |
|
Enables events to be sent and received over TCP sockets. |
|
Provides secure socket-based communication using SSL or TLS. |
|
Enables events to be sent and received as datagram packets. |
|
Enables event sending and receiving over VM, embedded memory, or persistent queues. |
|
WebSphere MQ Transport |
A Mule transport for WebSphere MQ. This transport is available with Mule Enterprise version 1.6 and later. |
The CXF Module allows remote web services to be invoked using their WSDL contract. |
|
Provides connectivity over the XMPP (Jabber) instant messaging protocol. |
Transport Matrix
| Name | Doc | I | O | Rq | Tr | St | Re | MEPs | Def MEP | Maven |
|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
one-way |
one-way |
org.mule.transport:mule-transport-ajax |
||
|
|
|
|
|
|
one-way |
one-way |
org.mule.transport:mule-transport-file |
||
|
|
|
|
|
|
org.mule.transport:mule-transport-ftp |
||||
|
|
|
|
|
|
one-way, request-response |
request-response |
org.mule.transport:mule-transport-https |
||
|
|
|
|
|
|
org.mule.transport:mule-transport-jdbc-ee |
||||
- |
|
|
|
|
|
|
one-way, request-response |
request-response |
org.mule.transport:mule-transport-jetty-ssl |
|
|
|
|
|
|
|
one-way, request-response |
request-response |
org.mule.transport:mule-transport-multicast |
||
|
|
|
|
|
|
one-way |
one-way |
org.mule.transport:mule-transport-pop3s |
||
|
|
|
|
|
|
one-way, request-response |
request-response |
org.mule.transport:mule-transport-rmi |
||
|
|
|
|
|
|
one-way, request-response |
one-way |
org.mule.transport:mule-transport-sftp |
||
|
|
|
|
|
|
one-way |
one-way |
org.mule.transport:mule-transport-smtps |
||
|
|
|
|
|
|
one-way |
one-way |
org.mule.transport:mule-transport-stdio |
||
|
|
|
|
|
|
one-way, request-response |
request-response |
org.mule.transport:mule-transport-tls |
||
|
|
|
|
|
|
one-way, request-response |
one-way |
org.mule.transport:mule-transport-vm |
Legend
-
Name - The name/protocol of the transport
-
Docs - Links to the JavaDoc (JD) and SchemaDoc (SD) for the transport
-
Inbound - (I) Whether the transport can receive inbound events and can be used for an inbound endpoint
-
Outbound - (O) Whether the transport can produce outbound events and be used with an outbound endpoint
-
Request - (Rq) Whether this endpoint can be queried directly with a request call (via MuleClient or the EventContext)
-
Transactions - (Tr) Whether transactions are supported by the transport. Transports that support transactions can be configured in either local or distributed two-phase commit (XA) transaction.
-
Streaming - (St) Whether this transport can process messages that come in on an input stream. This allows for very efficient processing of large data. For more information, see Streaming.
-
Retry - (Re) Whether this transport supports retry policies. Note that all transports can be configured with Retry policies, but only the ones marked here are officially supported by MuleSoft
-
MEPs - Message Exchange Patterns supported by this transport
-
Default MEP - (Def MEPs) The default MEP for endpoints that use this transport that do not explicitly configure a MEP
-
Maven Artifact - (Maven) The group name a artifact name for this transport in Maven