Nav
You are viewing an older version of this section. Click here to navigate to the latest version.

Available Transports

Following is a list of known transports (also called "providers") for Mule ESB. Some functionality is contained within modules instead of transports—​see Modules Reference. For more information on transports, see the following topics:

Mule Transports

Transport Description

AJAX Transport

The Mule AJAX connector allows Mule events to be sent and received asynchronously to and from the web browser

Abdera Transport

Allows you to easily integrate with Atom feeds and Atom Publishing Protocol servers via the Apache Abdera project.

EJB Transport

Allows EJB invocations to be made using outbound endpoints.

Email Transport

This transport supplies various email connectivity options.

File Transport

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.

FTP Transport

Allows files to be read / written to a remote FTP server.

HTTP Transport

This transport supplies HTTP transport of Mule messages between applications and other Mule servers.

HTTPS Transport

A secure version of the HTTP transport.

IMAP Transport

Connectivity to IMAP mail folders.

IMAPS Transport

A secure version of the IMAP transport.

JDBC Transport
Enterprise Edition

A transport for JDBC connectivity. Some of its features are available only in Mule Enterprise.

Jetty Transport

Provides support for exposing services over HTTP by embedding a light-weight Jetty server. For inbound endpoints only.

Jetty SSL Transport

A secure version of the Jetty transport.

JMS 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.

LDAP Transport

Allows you to send and receive Mule Messages to/from an LDAP directory.

POP3 Transport

Connectivity to POP3 inboxes.

POP3S Transport

A secure version of the POP3 transport.

Quartz Transport

Provides scheduling facilities with cron / interval definitions and allows Mule events to be scheduled/rescheduled.

RMI Transport

Enables events to be sent and received over RMI via JRMP.

Servlet Transport

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.

SMTP Transport

Connectivity to SMTP servers.

SMTPS Transport

A secure version of the SMTP transport.

SSL Transport

Provides secure socket-based communication using SSL or TLS.

STDIO Transport

This transport provides connectivity to streams such as System.in and System.out and is useful for ptesting.

TCP Transport

Enables events to be sent and received over TCP sockets.

TLS Transport

Provides secure socket-based communication using SSL or TLS.

UDP Transport

Enables events to be sent and received as datagram packets.

VM Transport

Enables event sending and receiving over VM, embedded memory, or persistent queues.

WebSphere MQ Transport
Enterprise Edition

A Mule transport for WebSphere MQ. This transport is available with Mule Enterprise version 1.6 and later.

WSDL Connectors

The CXF Module allows remote web services to be invoked using their WSDL contract.

XMPP Transport

Provides connectivity over the XMPP (Jabber) instant messaging protocol.

Transport Matrix

Transport Doc Inbound Outbound Request Transactions Streaming Retries MEPs Default MEP Maven Artifact

AJAX

JavaDoc, SchemaDoc

check

check

image

image

check

image

one-way

one-way

org.mule.transport:mule-transport-ajax

File

JavaDoc, SchemaDoc

check

check

check

image

check

image

one-way

one-way

org.mule.transport:mule-transport-file

FTP

JavaDoc, SchemaDoc

check

check

check

image

check

image

org.mule.transport:mule-transport-ftp-ee

HTTPS

JavaDoc, SchemaDoc

check

check

check

image

check

image

one-way, request-response

request-response

org.mule.transport:mule-transport-https

IMAPS

JavaDoc, SchemaDoc

check

image

image

image

image

image

one-way

one-way

org.mule.transport:mule-transport-imaps

JDBC

JavaDoc, SchemaDoc

image

image

image

image

image

image

org.mule.transport:mule-transport-jdbc-ee

Jetty SSL

JavaDoc, SchemaDoc

check

image

check

image

check

image

one-way, request-response

request-response

org.mule.transport:mule-transport-jetty ssl

Multicast

JavaDoc, SchemaDoc

check

check

check

image

image

image

one-way, request-response

request-response

org.mule.transport:mule-transport-multicast

POP3S

JavaDoc, SchemaDoc

check

image

check

image

image

image

one-way

one-way

org.mule.transport:mule-transport-pop3s

RMI

JavaDoc, SchemaDoc

check

check

check

image

image

image

one-way, request-response

request-response

org.mule.transport:mule-transport-rmi

SFTP

JavaDoc, SchemaDoc

check

check

check

image

check

image

one-way, request-response

one-way

org.mule.transport:mule-transport-sftp

SMTPS

JavaDoc, SchemaDoc

image

check

check

image

image

image

one-way

one-way

org.mule.transport:mule-transport-smtps

STDIO

JavaDoc, SchemaDoc

check

check

check

image

check

image

one-way

one-way

org.mule.transport:mule-transport-stdio

TLS

JavaDoc, SchemaDoc

check

check

check

image

check

image

one-way, request-response

request-response

org.mule.transport:mule-transport-tls

VM

JavaDoc, SchemaDoc

check

check

check

check(XA)

check

image

one-way, request-response

one-way

org.mule.transport:mule-transport-vm

Legend

Transport - The name/protocol of the transport
Docs - Links to the JavaDoc and SchemaDoc for the transport
Inbound - Whether the transport can receive inbound events and can be used for an inbound endpoint
Outbound - Whether the transport can produce outbound events and be used with an outbound endpoint
Request - Whether this endpoint can be queried directly with a request call (via MuleClient or the EventContext)
Transactions - 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 - 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 - 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 - The default MEP for endpoints that use this transport that do not explicitly configure a MEP
Maven Artifact - The group name a artifact name for this transport in http://maven.apache.org/[Maven]