ServiceMix 1.0: Apache 2.0 open source ESB based on JBI

Home

News: ServiceMix 1.0: Apache 2.0 open source ESB based on JBI

  1. The ServiceMix Team have just released the 1.0 version of ServiceMix, an open source enterprise service bus based on the Java Business Integration specification. This release adds RSS support and complete JCA integration.

    ServiceMix is an open source, Apache 2.0 licensed, ESB built from the ground up on JBI principles, semantics and APIs. ServiceMix includes a complete JBI container including the Normalised Message Service and Router, the JBI Management MBeans support for JBI deployment units and Ant tasks to install components and manage the container.

    In addition ServiceMix contains a suite of JBI Components such as:ServiceMix includes a fully integrated JCA container for high performance messaging and is fully integrated into Geronimo, Spring and JBoss.

    New and noteworthy in this release
    • a new RSS component for integrating and processing RSS news feeds in JBI
    • a sophisticated XPath and XSLT based XPath Router and transformer JBI component
    • migrated the JCA components to work with Jencks the Spring based JCA container which integrates with Geronimo JTA, JCA connectors and security components.
    For more details (and to download ServiceMix), please see the Release Notes. We welcome contributions.

    Threaded Messages (22)

  2. So Can It be installed/deployed in any J2EE container?
  3. So Can It be installed/deployed in any J2EE container?

    Absolutely. ServiceMix can run in any JVM via Spring or used inside a Servlet / EJB container.

    We've integrated ServiceMix into Geronimo to add JBI support and we've a JBoss deployer too.

    James
    LogicBlaze
  4. What would be great is a guide/example of how too package ServiceMix into an EAR file for deployment to J2EE compatible server. (1.3/1.4)

    The Geronimo and JBoss deployer examples seem to use platform specific features/deployment descriptions.

    I.e. how do I deploy service mix to listen on a JMS Connection factory / Queues combination looked up via JNDI and also listens for web service requests on the web tier of the J2EE server?
  5. What would be great is a guide/example of how too package ServiceMix into an EAR file for deployment to J2EE compatible server. (1.3/1.4)The Geronimo and JBoss deployer examples seem to use platform specific features/deployment descriptions.I.e. how do I deploy service mix to listen on a JMS Connection factory / Queues combination looked up via JNDI and also listens for web service requests on the web tier of the J2EE server?

    Good point, we'll do that. Up to now we've been creating our own JMS subscriptions using our own embedded JCA container

    http://servicemix.org/JCA

    or using our own embedded HTTP connector

    http://servicemix.org/HTTP

    But demonstrating this all working in an EAR is a great idea; I've raised an issue to track this - it shouldn't be too hard to do.

    Thanks for the suggstion Graham


    James
    LogicBlaze
  6. Looking forward to it.

    cheers

    Graham
  7. tutorial?[ Go to top ]

    Nothing ever beats a simple hand holding tutorial. Since this is a fairly new technology as well, it would be really nice to post a tutorial to demonstrate how to invoke different components with it. I know it is few days work, so it is up to your team.

    In any case, nice work. I am very interested in ESB. It is going to make our lives easier (though if integration becomes this easy, there will be a huge job loss).

    Vinay
  8. ServiceMix vs. Mule ESB[ Go to top ]

    What are similarities and differences between Mule ESB and ServiceMix?

    Simon
  9. ServiceMix vs. Mule ESB[ Go to top ]

    What are similarities and differences between Mule ESB and ServiceMix?Simon

    http://servicemix.org/How+does+ServiceMix+compare+to+Mule
  10. ServiceMix vs. Mule ESB[ Go to top ]

    What are similarities and differences between Mule ESB and ServiceMix?Simon
    http://servicemix.org/How+does+ServiceMix+compare+to+Mule

    Got it.
    Thanks
  11. tutorial?[ Go to top ]

    Nothing ever beats a simple hand holding tutorial. Since this is a fairly new technology as well, it would be really nice to post a tutorial to demonstrate how to invoke different components with it. I know it is few days work, so it is up to your team.

    Agreed! We're working on it. So far we've a getting started guide
    http://servicemix.org/Getting+Started

    together with a bunch of examples
    http://servicemix.org/Examples
    In any case, nice work. I am very interested in ESB. It is going to make our lives easier (though if integration becomes this easy, there will be a huge job loss).Vinay

    Despite what ESB vendors or WS-* evangelists might tell you, integration is hard! Tools like ESB make your lives much easier, taking care of the smart routing, protocol & transport switching, scaling and providing an easy way to transform and orchestrate things - but you've still gotta understand your business processes and then do the semantic integration. e.g. how does a purchase order in System A map to System X's idea of an order.

    So I think there's gonna be plenty of jobs in the integration space for some time to come :)

    James
    LogicBlaze
  12. Cool[ Go to top ]

    This looks cool. I must try it... and find a place to use it.

    .V
  13. Cool[ Go to top ]

    This looks cool. I must try it... and find a place to use it..

    Good point, certainly there is room for abuse here. I suspect we'll see a number of anti-patterns related to ESB in the coming years.

    --
    Igor Zavialov
    Factoreal Financial Data and Technical Analysis solutions.
  14. Cool[ Go to top ]

    Architectural stovepipe? <g>
  15. Cool[ Go to top ]

    ... and find a place to use it..V

    The worst antipattern people could ever run into...
  16. Cool[ Go to top ]

    ... and find a place to use it..V
    The worst antipattern people could ever run into...

    Yup! It's called "a solution looking for a problem" antipatern. But this does look cool. A bit like "Mule".

    .V
    http://roomity.com
  17. this is huge![ Go to top ]

    I think this is a HUGE announcement, not unlike JBoss way back. It will certainly have a large impact on my own work...

      just my 2 cents,
      gerald
  18. congrats - you quikies ![ Go to top ]

    great work - congrats to the servicemix team

    this is probably one of the quickest projects of this
    complexity that I have seen..

    you guys are model developers in my book

    --Arun
  19. can someone give an example business case where rules based routing is required
  20. can someone give an example business case where rules based routing is required

    Its just an extension of content based routing. e.g. to implement service level agreements, to alert operators if things to wrong or to load traffic to different servers based on the users' rating (gold customers get those big fast boxes etc).

    James
    LogicBlaze
  21. Can someone at TSS please adjust the title of this to accurately reflect reality? There is a huge difference between an "Apache 2.0 open source ..." thing and an "Apache 2.0 *licensed* open source ..." thing. The title as it stands is incredibly misleading.

    Craig McClanahan
  22. ESB vs traditional integration tool[ Go to top ]

    What is the difference???

    If you take a look at the ServiceMix 1.0's ESB features, most of them are provided by some commercial integration software, like wli or tibco. To me, it seems ESB and integration are the same thing.

    Any idea?

    Rick
  23. ESB vs traditional integration tool[ Go to top ]

    What is the difference???If you take a look at the ServiceMix 1.0's ESB features, most of them are provided by some commercial integration software, like wli or tibco. To me, it seems ESB and integration are the same thing.Any idea?Rick

    Conceptually integration softare and ESBs solve similar kinds of problems

    * Protocol Switching/Adapters
    * Smart Routing
    * Transformations
    * Orchestration
    * Management

    The main difference between them is their use of standards (APIs and WS-*), what technologies they use and how they work.

    e.g. ServiceMix is based on the JBI standard and can work with any web service and SOAP stacks, integrates with JBI-compliant BPEL engines and has a suite of pluggable transports and protocols including Jabber, JMS, JCA and RSS.

    James
    LogicBlaze