The latest release of IBM Integration Bus has just been announced. IBM Integration Bus V10.0 includes enhancements which can help improve developer experience, manageability, cloud, and functional capabilities.
IBM Integration Bus for V10.0
IBM Integration Bus for z/OS V10.0

The key features include

  • Quickly get started with a radically simplified, single-package installation and improved support for unit test
  • Flexibly interact with WebSphere MQ using connection policies
  • Use Integration Bus without installing WebSphere MQ
  • Simplify administration of Integration Bus by using the improved web browser user interface which includes new capabilities for deployment, creating, editing and attaching policy documents
  • Rapidly create REST APIs and use the new, graphical data mapper to support the transformation of unmodelled data structures
  • Reuse common resources, such as message models, subflows, Java, and ESQL code in shared libraries
  • Integrate publish-subscribe-based applications by using MQ Telemetry Transport messages
  • Easily transform and model data structures with multiple new Graphical Data Map and DFDL features
  • Extend the reach of the Integration Bus with file, database, and security enhancements
  • Create new application connectors and control them by using independently managed policies
  • Import and convert existing WebSphere Enterprise Service Bus integration assets
  • Share product extensions with the integration community, including an enhanced explorer configured to access a GitHub repository of Integration Bus patterns




5 comments on"The new IBM Integration Bus for V10.0 release has been announced for InterConnect 2015"

  1. Hi..

    Can we do with IIB v10 ,whatever operations done by MQ ?

    • Ian_Larner July 12, 2016

      Hi @bharathi,
      We’re not entirely sure about what you’re referring to with the phrase “operations done by MQ”, so apologies in advance if we misinterpret what you’re asking here …
      With versions before IIBv10, the IBM Integration Bus product had a pre-requisite of an MQ installation for all IIB runtime installations. There was a 1 to 1 relationship defined between an IIB node and an MQ queue manager. This queue manager was used by the IIB for several internal architectural purposes such as for communications between the IIB Toolkit and the runtime IIB node, as a means for distributing IIB information via publish/subscribe for monitoring events and statistics about how IIB is performing, as a state store for some of the IIB flow nodes, for coordinating two-phase commit XA transactions and for authorising users carrying out administration tasks.
      With IIBv10, the architecture of the product changed and many of these tasks now have alternatives within IIB such that a user does not have to install MQ if they do not wish to. IIBv10 has also re-engineered the MQ nodes in message flows to use MQ Client connections to a remote queue manager if you would like. There are still some situations where MQ is required, which are well documented in our Knowledge Center. Because of this, users still have entitlement to install MQ if used for IIB purposes. This licensing position is the same in IIBv10 as it was in earlier versions.
      Taking another possible slant on your question, IIB and MQ are complementary products: IIB is not a messaging provider in and of itself, and does not try to be. IIBv10 does provide an MQTT server (for the product’s own pub/sub purposes) out of the box which provides some messaging capabilities, but this is designed for different use cases than MQ.
      Does this make sense for your question?

  2. MQ is still used (which is a very good thing) by some of the IIB nodes.

    Use MQ if you value your business data. Use files or http if you don’t.

  3. Hi, MQ license we need to buy seperately.


Join The Discussion

Your email address will not be published. Required fields are marked *