iStock_000020343379_XXXLargeWe’re very pleased to announce the availability of IBM Integration Bus v10.0.0.11. Fix pack releases, published every quarter, provide both regular maintenance for the product, and also new functional content. This blog post summarises all the latest and greatest capabilities:

  • Use the new App Connect REST Request node and Pattern
  • Send Activity Log data to IBM Cloud
  • IBM Integration Bus is now upgraded to use Java 8
  • Platform support extended to include Ubuntu 16.04
  • IIB Developer Edition Docker image can now be downloaded for free from Docker Registry Hub
  • IBM Integration Bus is now available on IBM Cloud Private

Expand the sections below to find out more!

Use the new App Connect REST Request node and Pattern

Fix pack 11 provides a new App Connect REST Request node which can be placed in a message flow to issue requests to an IBM App Connect REST API. The node uses an imported Swagger document (in either JSON or YAML format), which defines the REST API and the operations that are available. When you have downloaded the API, you can import it into your IIB Toolkit workspace and on the App ConnectREST Request node’s properties, select the operations that you want to invoke. The App Connect REST Request node is contained in the Cloud Connectors drawer of the flow palette, and is represented in the IBM Integration Toolkit by the following icon:

To make it even easier to link IBM Integration Bus and App Connect there is also a new pattern available in the IIB Toolkit Pattern Explorer view:

The pattern will generate you a sample IIB message flow which can be driven using MQ, HTTP or File transports. The flow will create a simple JSON request message of the right format (using either a Compute, JavaCompute or graphical Mapping node) which can be used to invoke an App Connect REST API.

The IIB pattern also generates an App Connect template which can be imported into the App Connect Designer Web UI tooling so that you have an App Connect REST API flow ready to communicate with your SaaS application of choice.

Send Activity Log data to IBM Cloud

For a while now, IIB installations have been able to send operational information to a centralised dashboard hosted on IBM Cloud:

Fix pack 11 extends these facilities further to also include Activity Log information. To enable the reporting of Activity Log data to IBM Cloud Log Analysis, you must first enable your IBM Integration Bus integration servers to send logging information to the service, and then configure an ActivityLog configurable service to send the Activity Log data to Log Analysis.

 mqsichangeproperties TESTNODE -c ActivityLog -o ActivityLogConfigurableServiceName -n bluemixReporting -v true

For more information, see Reporting Activity Log data to IBM Cloud Log Analysis.

IBM Integration Bus is now upgraded to use Java 8

Starting with Fix Pack 11, IBM Integration Bus now ships with Java 8 on all supported distributed platforms except Solaris and HP. IBM Integration Bus v10 on z/OS also supports Java 8 as a prerequisite component from IIB onwards. There are some limitations with the Java 8 support for application developers, and after applying the fix pack you may encounter known issues which are caused as a result of upgrading to Java 8 if you try to move back to an earlier fix pack (where Java is not yet at v8). If you have any concerns about this, then please read about the details in this accompanying article.

Platform support extended to include Ubuntu 16.04

This fix pack also adds Ubuntu 16.04 Long Term Service release to our supported platforms.

IIB Developer Edition Docker image can now be downloaded for free from Docker Registry Hub

There is now a pre-built IIB Docker image available for easy download from the Docker Registry Hub website!

The image contains a pre-installed Developer Edition licensed IIB at the latest fix pack level. Starting from this Docker image, you can run a container which will create and start an Integration Node to which you can deploy integration solutions. You can optionally specify an Integration Node name using the NODENAME environment variable and an Integration Server name using the SERVERNAME environment variable. After downloading the image, to run it, use a command like this:

 docker run --name myNode -e LICENSE=accept -e NODENAME=MYNODE -e SERVERNAME=MYSERVER -P iib

If you wish, you can also deploy an IBM Integration Bus BAR file by specifying a Docker volume which makes the BAR file(s) available when the container is started:

 docker run --name myNode -v  /local/path/to/BARs:/tmp/BARs -e LICENSE=accept -e NODENAME=MYNODE -e SERVERNAME=MYSERVER -P iib

Remember, if you want to build an IIB image the way you like it, that’s fine too. If you want a head start, you can find the scripts we used on Github.

IBM Integration Bus is now available on IBM Cloud Private

Since fix pack was released at the beginning of September, IBM has announced and brought to market our next generation private cloud platform, IBM Cloud Private (V2.1). IBM Cloud Private includes a Catalog providing a simple, self service, access to IBM and Open Source software which has been built for Kubernetes. This catalog is a collection of Deployment Packages (using Helm charts) displayed as tiles, which provide access to software under separate license terms.

For more information on deploying IIB to IBM Cloud Private, check out our Knowledge Center

Helm is the open standard for Application Packaging and Deployment for Kubernetes. IIB has its own Helm chart which we have also made freely available outside of IBM Cloud Private, should you wish to use this to help deploy IIB in a Kubernetes environment:

Helm charts automate the deployment of resources and prereqs including locations of Docker images. The IIB Helm chart lets you control things like the number of processors and amount of memory assigned to the IIB Docker image by the Kubernetes system:

4 comments on"Explore the new features in IBM Integration Bus version"

  1. Bhaskar Rajamani March 24, 2018

    we are getting some MQMD related error @ IIB 10 Fix pack 10 and 11 ( so far tested ) not occurred in IIB fix pack 7 and 8

    going to raise a ticket

    Error Message :
    ( TSTIIBBK1.ZeusOnlineIntegrationServer ) Unable to backout a message; MQPUT to queue ”ZS.ESB.HOUSEHOLDAPP.IN.BOQ” failed: MQCC=’2′; MQRC=’2252′.

    The message was unable to be backed out, because it failed to put the message to either the backout requeue queue or the WebSphere MQ dead letter queue, which is defined as queue ”ZS.ESB.HOUSEHOLDAPP.IN.BOQ”.

    Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, and take the appropriate action. You might have to restart the integration node after you take this recovery action.

  2. I am not able to retrieve the fixpack is getting failed.It is urgently required for my project

    Please address the issue.I am looking forward to use Java8 jars soon.

    • BenThompsonIBM January 16, 2018

      Hi shwetabh,
      Thanks for your comment, and I’m sorry to hear that you are unable to download the fixpack. I just navigated to the fix pack on Fix Central and was able to download without any problems … I downloaded for Windows for which the direct link is here … if you are on another platform you should be able to follow the links at the base of this page. If you continue to hit problems downloading then the best thing to pursue diagnostics (perhaps this could be related to your entitlement?) would be to report the problem through the usual service channel for investigation.
      Best Regards, Ben

Join The Discussion

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