servicemix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache ServiceMix 4.0 > Technology selection guidelines
Date Mon, 25 Jan 2010 15:05:00 GMT
    <base href="">
            <link rel="stylesheet" href="/confluence/s/1519/1/1/_/styles/combined.css?spaceKey=SMX4&amp;forWysiwyg=true"
<body style="background-color: white" bgcolor="white">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="">Technology
selection guidelines</a></h2>
    <h4>Page  <b>added</b> by             <a href="">Gert
    <div class="notificationGreySide">
         <p>ServiceMix 4 offers a set of different messaging and integration technologies:</p>

<p>Depending on the solution you're building, you want to select one or more of these
technologies.  Below are some guidelines to help you pick the right mix for your problem.</p>

<h2><a name="Technologyselectionguidelines-StartingwithCamel"></a>Starting
with Camel</h2>
<p>For any integration scenario, we recommend to start as simple as possible.  Camel
allows you to build routes for integration scenario's quickly and efficiently.  You can deploy
these routes directly on ServiceMix by deploying the plain Spring XML route or by packaging
the route in an OSGi bundle. </p>

<p>As you need more (advanced) features, start combining Camel with ActiveMQ, CXF and/or
the NMR</p>

<h2><a name="Technologyselectionguidelines-AddActiveMQforenterpriselevelmessaging"></a>Add
ActiveMQ for enterprise-level messaging</h2>
<p>ActiveMQ is a JMS message broker, featuring support for clustering, pluggable persistence
mechanism, master-slave configuration for failover, ...</p>

<p>ServiceMix 4 includes an instance of the ActiveMQ broker, which can be combined with
Camel to provide easy-to-use message persistence and reliable messaging.</p>

<p>After setting up multiple instances of ActiveMQ (or ServiceMix 4) on the network,
you can configure ActiveMQ clustering or master-slave mode to allow for a more reliable and
scalable set-up.</p>

<h2><a name="Technologyselectionguidelines-AddCXFforyourwebserviceintegrationneeds"></a>Add
CXF for your webservice integration needs</h2>
<p>CXF is an open-source services framework that you can use to suit your WS-* standards
integration needs.  It allows you to use common programming APIs like JAX-RS or JAX-WS for
building your own services and to expose them to the outside world.</p>

<p>You can use CXF from within your Camel routes with the Camel CXF component.</p>

<h2><a name="Technologyselectionguidelines-AddtheNMRfornormalizedmessaging"></a>Add
the NMR for normalized messaging</h2>
<p>The NMR provides the basic ESB features for ServiceMix 4.  You can use it to connect
multiple camel routes in a lightweight way.  It can also be used as a common transport on
which you can add container-level auditing by registering your own ExchangeListener implementation.</p>

<h2><a name="Technologyselectionguidelines-JBIforBPELandforexistingJBIusers"></a>JBI
for BPEL and for existing JBI users</h2>
<p>If you want to build a full-blown SOA solution using BPEL, ServiceMix includes a
version of Apache ODE that integrates well with JBI messaging.  Because we still support JBI
1.0 on ServiceMix, you can also move your existing JBI artifacts from ServiceMix 3 to the
new container with no/minimal changes.</p>

    <div id="commentsSection" class="wiki-content pageSection">
       <div style="float: right;">
            <a href=""
class="grey">Change Notification Preferences</a>
       <a href="">View
       <a href=";showCommentArea=true#addcomment">Add

View raw message