6 Replies Latest reply on Mar 24, 2009 7:34 AM by Gary Motts

    Why Fuse Message Broker?

    Gary Motts Novice

       

      Fuse ESB implements ActiveMQ as its JMS provider. Can someone describe to me why Fuse Message Broker would be used in addiiton to Fuse ESB? Is the Fuse ESB a vanilla implementation of the JMS spec using Active MQ?

       

       

        • 1. Re: Why Fuse Message Broker?
          Ulhas Bhole Novice

          FUSE ESB is certified version of Apache Servicemix products which do use ActiveMQ as JMS borker but implements JBI specification (and OSGi in Servicemix 4).

           

          FUSE Message Broker is the product that is certified version of Apache ActiveMQ which implements JMS specification.

           

          Ulhas

          • 2. Re: Why Fuse Message Broker?
            Gary Motts Novice

            Thanks for the response, let me restate the question, I'm developing on ServiceMix ESB which has ActiveMQ JMS provider .  Is there any reason why I should use Fuse Message Broker?

             

            In one of the sample Logistics examples (image attached), Fuse Message Broker is used in conjunction with ServiceMix ESB.  I'm trying to understand what Fuse Message Broker offers that the ServiceMix ActiveMQ JMS provider does not.  They both implement the JMS 1.1 spec.....

            • 3. Re: Why Fuse Message Broker?
              Ulhas Bhole Novice
              gmotts wrote:

              Thanks for the response, let me restate the question, I'm developing on ServiceMix ESB which has ActiveMQ JMS provider .  Is there any reason why I should use Fuse Message Broker?

               

              I think what you are referring to is servicemix-jms component which is a JBI component that allow you to talk to any JMS broker (not just ActiveMQ) that implements JMS specs.

               

               

               

              In one of the sample Logistics examples (image attached), Fuse Message Broker is used in conjunction with ServiceMix ESB.  I'm trying to understand what Fuse Message Broker offers that the ServiceMix ActiveMQ JMS provider does not.  They both implement the JMS 1.1 spec.....

               

              As I said earlier in this post what you are referring to is servicemix-jms component which is independent of the broker, there is no ActiveMQ specific JBI component.

              Servicemix won't provide the Messaging functionality but allow you to talk to Messaging infrastructure like JMS Broker using JBI component (e.g. servicemix-jms).

               

              Please do not get confused with 2 product as  one implements JBI specs. and other JMS. servicemix can talk to ActiveMQ (jms specs.) using a JBI component (servicemix-jms).

               

              Ulhas

              • 4. Re: Why Fuse Message Broker?
                Gary Motts Novice

                For both ServiceMix/Iona Fuse - Apache ActiveMQ is the messaging foundation which provides reliability, enables a distributed environment + clustering and yes, ServiceMix/Iona Fuse implement the JBI spec for which enables creating binding components to send/receive messages from the NMR to other JMS providers.

                 

                When I download and install Iona (Progress) Fuse ESB v3.3.14, is Fuse Message Broker and Fuse Mediation Router already bundled within the executable?  I'm looking to implement a publish/subscribe model where our systems publish messages to a topic queue defined in Apache MQ (provided by the ESB) and receive the response as a durable subscription.  If Fuse Message broker is separate, I'm looking for product differences and advantages for its use.

                 

                Edited by: gmotts on Mar 23, 2009 9:55 AM

                • 5. Re: Why Fuse Message Broker?
                  Ulhas Bhole Novice
                  gmotts wrote:

                  When I download and install Iona (Progress) Fuse ESB v3.3.14, is Fuse Message Broker and Fuse Mediation Router already bundled within the executable?  I'm looking to implement a publish/subscribe model where our systems publish messages to a topic queue defined in Apache MQ (provided by the ESB) and receive the response as a durable subscription.  If Fuse Message broker is separate, I'm looking for product differences and advantages for its use.

                   

                   

                  In certain scenarios, where you have mixed deployments in FUSE ESB (e.g. some components/flows that do not use JMS and some that use JMS interaction) you might use external JMS implementation like separate FUSE Message Broker/ActiveMQ  for overall manageability. It is useful especially when you need to adjust you borker configuration or some other tasks which might result in some downtime. In mixed deployment only components/flows affected will be the ones that use JMS when you use external broker. If you are not aiming at the mixed environment and using Service Assemblies/flows that only involve JMS interaction then you can avoid having separate JMS broker and use embedded one.

                   

                  As for the advantage of using internal broker is that you are using the compatible Message Broker which which all the testing was done as part of the FUSE ESB release cycle. (BTW, you can ensure the same with standalone broker as long as you use the same version as the internal broker) Both standalone and embedded FUSE Message Brokers have gone through the same comprehensive testing cycles before the release.

                   

                   

                  Ulhas

                  • 6. Re: Why Fuse Message Broker?
                    Gary Motts Novice

                    Thank you! That answsers my questions