iStock_000020343379_XXXLargeWe’re thrilled to announce the availability of IBM App Connect Enterprise v11.0.0.2. This is the second fix pack released for App Connect Enterprise software. We provide fix packs on a regular cadence, approximately once per quarter, with one more intended to come this calendar year. Fix packs provide both regular maintenance for the product, and also new functional content. This blog post summarizes all the latest and greatest capabilities:

  • There are no longer Technology Preview restrictions on the Integration Node and Node-wide HTTP listener
  • IBM App Connect Enterprise Toolkit Eclipse upgrade
  • Logging to standard out in JSON format
  • Admin security permissions can be applied using file or MQ based configuration for both nodes and servers

Expand the sections below to find out more!

There are no longer Technology Preview restrictions on the Integration Node and Node-wide HTTP listener

Existing users of IBM Integration Bus will be very familiar with the concept of an integration node. Architecturally speaking, an integration node is a parent process which is responsible for looking after one or more associated integration server processes. An Integration Server is used to provide an isolated runtime environment for a set of deployed message flows and resources. In August, ACEv11.0.0.1 reintroduced the integration node concept with a Technology Preview classification which advised users that it was not intended for production use. The Technology Preview classification is now removed with ACEv11.0.0.2 It is now fully supported for users to take ACEv11.0.0.2 Integration Nodes and Integration Node-wide listeners into production.

IBM App Connect Enterprise Toolkit Eclipse upgrade

Developers create integration artifacts such as message flows, message models, graphical maps and code using the IBM App Connect Enterprise Toolkit. This integrated development environment can be connected to runtime integration servers (both those which are owned by integration nodes, and those which exist independently as standalone processes) for the purpose of deploying and testing flows. ACEv11.0.0.2 includes an upgrade of the toolkit component to utilize Eclipse version 4.4.2. The Flow Exerciser component of the Toolkit has also been enhanced to enable the injection of data, and saving of messages which can be done with node owned or standalone integration servers:

Logging to standard out in JSON format

App Connect Enterprise integration servers can log directly to standard out in the command shell from which they are started. For some users this provides a strong usability enhancement compared to the standard approach of IBM Integration Bus which used the system log for recording this kind of information:

From ACEv11.0.0.2 we have added a new setting in the server.conf.yaml file which lets you specify that these log entries should be made in a JSON format (as opposed to the human readable default form shown above). This can be very useful for those executing ACE in a container environment for example, who wish to scrape these log entries in a programmatic way, for the purpose of populating other logging frameworks such as an ELK stack for example. The relevant section of the server.conf.yaml file is shown below:

The output which is generated from the integration server when using the ibmjson setting looks like this:

Admin security permissions can be applied using file or MQ based configuration for both nodes and servers

Web users communicating with IIB using its administration REST API can be mapped to defined roles which grant or deny permission to execute a set of administration tasks. These permissions are assigned using settings applied using a file based model, or due to the historical connection between an integration node and a queue manager, they could also be applied using an MQ queue based model. ACEv11.0.0.1 provided a very similar file based approach, but now with the release of ACEv11.0.0.2 users have the opportunity to use the MQ queue based approach as well. The permissions model has also been extended in ACEv11.0.0.2 so that it can be applied to individual integration servers, making it even easier to secure a network of intergation servers deployed within a container-based system such as IBM Cloud Private or Kubernetes. Examples for the relevant settings can be found in the node.conf.yaml file as shown below:

13 comments on"Explore the new features in App Connect Enterprise version"

  1. As mentioned by Ben, the ACE Toolkit’s Timer nodes are not yet supported. by when it will be included?

    • BenThompsonIBM November 22, 2018

      Hi Shobha, I’m afraid in order to safely avoid accidentally recognising revenue for features which have not yet been delivered, IBM is always very cautious about publicly discussing specific dates for delivery of future pieces of function without Non-Disclosure agreements in place and to ensure the relevant caveats are placed around our future estimates so as to avoid disappointing anyone. If you’re not already a member of our Early Access Program, can I recommend you sign up so you can keep as close as possible to our future plans. Cheers, Ben

  2. Are there any new nodes have been introduced? What are the new features have been introduce from developer perspective?

    • BenThompsonIBM November 22, 2018

      Hi Shobha, Fix pack 2 for App Connect Enterprise software, which this article discusses, does not include any new message flow nodes. In general we do periodically add further new message flow nodes to the product through the fix pack delivery mechanism – for example in the last fix pack ACEv11.0.0.1 we added the Group nodes. Cheers, Ben

  3. ACE v11.0.02 on cloud – is it supports all the nodes ? like Timer and Aggregation nodes?

    • BenThompsonIBM November 20, 2018

      Hi Vishnu, the ACE Toolkit’s Timer nodes are not yet supported, but we do have the Scheduler node in the App Connect Designer tool, which you can integrate with a Toolkit flow using our callable flow nodes. As for the Aggregation nodes, these are stateful and built on top of MQ when used in the ACE software product, but we do have the Group nodes which are supported for deployment to the cloud, and which provide the same functions but as a stateless set of nodes which use in-memory queueing instead.

  4. Great set of new functionality – onward and upwards with the ACE Team!

  5. ACE Fix Packs can no longer be downloaded without entitlement/support contract… 🙁
    when will App Connect Enterprise for Developers be updated to V11.0.0.2?

    • @Michael Dag Hi,
      IBM App Connect Enterprise for Developers has been updated to V11.0.0.2.
      Regards, Ian

  6. Hi @BenThompsonIBM – Please can you comment the download link for IBM App Connect Enterprise v11.0.0.2 Developer edition.

Join The Discussion

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