A simple presentation for Mule Jetty Transport.

1. By – Ankush Sharma

2. Jetty is a Java HTTP (Web) server and Java Servlet container. While Web Servers
are usually associated with serving documents to people, Jetty is now often used for
machine to machine communications, usually within larger software frameworks.

3.  The Jetty transport provides support for exposing applications over HTTP by
embedding a light-weight Jetty server. The Jetty SSL Transport works the same
way but over SSL. You can only define inbound endpoints with this transport.
 The connector allows Mule to expose Mule Services over HTTP using a Jetty
HTTP server. A single Jetty server is created for each connector instance. One
connector can serve many endpoints. Users should rarely need to have more than
one Jetty connector. The Jetty connector can be configured using a Jetty XML
config file, but the default configuration is sufficient for most scenarios.

5.  Following are the options on general tab –
 Display Name – The name of the component to be displayed in Mule flow.
 Exchange Pattern – The exchange pattern that will be used by this component.
 Address – Address for Jetty connector.
 Connector Configuration – Reference to the global connector configuration.

7.  Following are the options on advanced tab –
 Encoding – Encoding standard to be applied on message data.
 MIME Type – MIME type of message data e.g. application/xml.
 Connector Endpoint – Reference to the global connector endpoint configuration.

9.  Following are properties on reconnection tab –
 Do not use a Reconnection Strategy – This is the default radio button which specifies do
not try to reconnect if there is error connecting to the web address URL.
 Standard Reconnection – Use this radio button to enable a standard reconnection
strategy.
 Frequency (ms) – The frequency time in milliseconds after which the File connector will try to
access the web address URL.
 Reconnect Attempts – This tells how many times the File connector will try to connect to web
address URL.
 Reconnector Forever – Check this box if there is need to make File connector connect to web
address URL until there is a successful connection with it.
 Custom Reconnection – Use this radio button to create a custom Reconnection strategy.
 Class – The java class which will come in action after a failed connection attempt.
 Run the connection in a separated thread – Check this box if there is need to use this custom
reconnection operation in separate thread.

11.  Following are properties on Transformers tab –
 Global transformers – Enter a list of synchronous transformers that are applied to the
request before it is sent to the Jetty transport.
 Transformers to be applied - Enter a list of synchronous transformers that are applied to
the response before it is dispatched from the Jetty transport.

12.  Following are options on HTTP Settings tab –
 User – The username that will be used for authentication.
 Password – Password for the username.
 Content Type – The HTTP content type to use.

13.  Notes tab - This tab is used to add special notes for the Jetty transport.
 Metadata tab – This tab is used to add any metadata entry for Jetty transport.