New function added in Version 10.0 fix packs

Some fix packs and other maintenance packs deliver new functions.

The What's new in Version 10.0? topic introduces you to the main new function in IBM Integration Bus Version 10.0. This topic introduces you to the additional function, which is additional to maintenance fixes, that is added in fix packs.

For detailed information about the contents of fix packs and other maintenance packs, see the IBM Support support web page, where you can access additional information about IBM Integration Bus.

Fix pack V10.0.0.24 enhancements

Maintenance fixes only.

Fix pack V10.0.0.23 enhancements

Maintenance fixes only.

Fix pack V10.0.0.22 enhancements

Maintenance fixes only.

Fix pack V10.0.0.21 enhancements

Maintenance fixes only.

Fix pack V10.0.0.20 enhancements

Maintenance fixes only.

Fix pack V10.0.0.19 enhancements

For details of the new feature in IBM Integration Bus Version 10.0 fix pack V10.0.0.19, see the following section:

LDAP authorization

Support for LDAP authorization

You can authorize roles in IBM Integration Bus against a Lightweight Directory Access Protocol (LDAP) or Secure LDAP (LDAPS) server. You can grant and revoke administration authority for an integration node and each of its managed integration servers by configuring LDAP authorization for specified groups or attributes in LDAP to specified roles in IBM Integration Bus.

For more information, see Configuring authorization by using LDAP groups.

Fix pack V10.0.0.18 enhancements

Maintenance fixes only.

Fix pack V10.0.0.17 enhancements

Maintenance fixes only.

Fix pack V10.0.0.16 enhancements

For details of the new feature in IBM Integration Bus Version 10.0 fix pack V10.0.0.16, see the following section:

Exception log resource manager

Exception log resource manager
The exception log resource manager is introduced to provide the ability to capture, in an exception log, data relating to exceptions that occur at any time during processing on an integration server. The exception log contains data, including BIP error messages, that allows message flow developers and administrators to quickly diagnose issues.

For more information, see Enabling the exception log.

Fix pack V10.0.0.15 enhancements

Maintenance fixes only.

Fix pack V10.0.0.14 enhancements

For details of the new features in IBM Integration Bus Version 10.0 fix pack V10.0.0.14, see the following sections:

Group nodes: aggregation scenarios that do not require an IBM MQ queue manager

Creating message flows that use the Group nodes to provide stateless aggregation scenarios
The Group nodes are introduced to provide the ability to create fan-out/fan-in style static and dynamic aggregation scenarios that are stateless without requiring an IBM MQ queue manager to be available for the integration server. They provide an alternative to the Aggregation nodes that require the provision of an IBM MQ queue manager.

For more information, see Group nodes and aggregation nodes.

FTPS as a transport protocol

FileInput, FileRead, and FileOutput nodes support FTPS as a transport protocol

You can configure your message flows to use the FTPS transfer protocol when handling files. The Transfer protocol property on the FileInput, FileRead, and FileOutput nodes provides the option to select FTPS when you are working with files in a remote file system.

For information about working with files, see Working with files.

JMS shared subscriptions

Creating shared subscriptions

The Shareable subscription property is introduced on the JMSInput node to allow the creation of shared subscription when working with a JMS 2.0 compliant provider.

For more information, see JMSInput node.

Fix pack V10.0.0.11 enhancements

For details of the new features in IBM Integration Bus Version 10.0 fix pack V10.0.0.11, see the following sections:

Cloud connectivity

Connectivity between IBM Integration Bus and IBM App Connect

An AppConnectRESTRequest node is provided, which enables interaction between IBM Integration Bus and an App Connect REST API. The AppConnectRESTRequest node uses an imported Swagger document, which defines the REST API and the operations that are available. An App Connect REST Request pattern is also available, which you can use to configure the connection between IBM Integration Bus and the App Connect REST API.

For more information, see Connecting to an App Connect REST API.

Platforms and environments

Support for Java™ 8

The Java SDK that is provided on toolkit platforms, and the Java JRE that is provided on runtime-only platforms, have been upgraded to Java 8. This upgrade means that you can now deploy JAR files that have been built using Java 8 to the IBM Integration Bus runtime.

For more information, see IBM Integration Bus v10 support for Java 8.

Fix pack V10.0.0.10 enhancements

Docker support in IBM Integration Bus

Running IBM Integration Bus in a Docker container

Support is provided for running IBM Integration Bus in a Docker container. You can choose to build specific configurations into your IBM Integration Bus Docker images, such as integration servers that already have particular applications deployed, or you can choose to start up a Docker container from the image and then deploy changes to the running integration node.

You can create your own Docker images, or you can download an image of the IBM Integration Bus for Developers edition from https://hub.docker.com/r/ibmcom/iib/ and run this in a Docker container.

For more information, see Configuring IBM Integration Bus to run in Docker.

Deploying IBM Integration Bus to IBM Cloud Private

Deploying IBM Integration Bus and IBM Integration Bus for Developers to IBM Cloud Private

Support is provided for deploying the Developer Edition or Advanced Edition of IBM Integration Bus to the IBM private cloud, by using Helm Charts. The Developer Edition is available free of charge for evaluation, development, and test purposes, but not for use in a production environment. If you have purchased a license for IBM Integration Bus Advanced Edition, you can deploy that version of the product to IBM Cloud Private.

For more information, see Deploying IBM Integration Bus to IBM Cloud Private and Deploying IBM Integration Bus for Developers to IBM Cloud Private.

Report resource statistics to a file in the filesystem

Reporting resource statistics directly to the filesystem

You can arrange for resource statistics to be written directly to the filesystem. If you enable this option, each resource manager writes a separate file that contains its resource statistics.

For more information, see Reporting resource statistics to files.

Import Swagger documents that contain recursive self references

Importing Swagger documents that contain recursive self references

The restriction on the import of Swagger documents that contain recursive self references is lifted and applies to situations when you do not intend to use graphical maps, or you intend to use mappings only by using a Move transform from input to output.

For more information, see Restrictions on Swagger documents.

XPath cache enhancements

Enhancements to XPath cache operation

The integration server XPath cache has been enhanced. You can now control the frequency with which activity log messages are emitted by the XPath cache. You can also opt to disable the cache and this action might be useful in a highly multi-threaded environment where many XPath expressions are evaluated on each message flow invocation and there might be thread contention on the cache.

For more information, see Configuring the XPath cache.

Export remote integration node connection details to a .broker file

Exporting connection details of a remote integration node to a .broker file

To facilitate the creation of connection files for use when you connect to remote integration nodes, you can now use the IBM Integration Toolkit to export the connection details of a remote integration node to a .broker file.

For more information, see Connecting to a remote integration node.

Extension to the mqsicvp command for CPU benchmark processing

Using the mqsicvp command for CPU benchmark processing

The mqsicvp command is extended to allow you to perform CPU benchmark processing. The benchmark tests CPU performance by calculating a recursive, arithmetic sequence on one or more threads.

For more information, see mqsicvp command.

Specify digest format for the password for an outbound username token

Specifying digest format for the password for an outbound username token

By using the Policy Set Bindings section of the editor in the IBM Integration Toolkit, you can specify that the password for an outbound username token is created in digest format instead of in plain text format. This option is applicable only to consumer bindings.

For more information, see Policy Sets and Policy Set Bindings editor: Authentication and Protection Tokens panel.

Fix pack V10.0.0.9 enhancements

For details of the new features in IBM Integration Bus Version 10.0 fix pack V10.0.0.9, see the following sections:

Routing requests through an HTTP proxy server

Sending requests to an HTTP proxy server that requires authentication
You can configure the following message flow nodes to route requests through an HTTP proxy server that requires a user name and password:
  • HTTPAsyncRequest
  • HTTPRequest
  • RESTAsyncRequest
  • RESTRequest
  • SalesforceRequest
  • SOAPAsyncRequest
  • SOAPRequest

You can use the mqsisetdbparms command to provide the credentials in an httpproxy:: ResourceName. The ResourceName takes either the form httpproxy::proxyHostname, where proxy_hostname matches the host name specified in the HTTP(S) proxy location property on the node, or httpproxy::HTTPPROXY, which can be used as a default for any proxy server that does not have a matching httpproxy::proxyHostname setting.

For more information, see Routing requests through an HTTP proxy server that has authentication enabled.

Routing requests to Salesforce through an HTTP proxy server

You can configure the SalesforceRequest node to send requests through an HTTP proxy server, by specifying the location of the proxy server on the HTTP(S) proxy location parameter.

If the HTTP proxy server has been configured to require authentication through a user name and password, you can use the mqsisetdbparms command to provide these credentials on the httpproxy:: resource name. For more information, see Routing requests through an HTTP proxy server that has authentication enabled.

Fix pack V10.0.0.8 enhancements

For details of the new features in IBM Integration Bus Version 10.0 fix pack V10.0.0.8, see the following sections:

Asynchronous callable flow nodes

Splitting message flow processing asynchronously between different locations

The support for callable message flows has been extended to include support for asynchronously callable message flows. You can split processing between asynchronously callable flows by using the CallableFlowAsyncInvoke and CallableFlowAsyncResponse nodes. For more information, see Developing asynchronously callable message flows.

You can also choose to share data between the flows that contain these nodes (the calling flow and the response flow) by storing and retrieving data in the UserContext folder in the Environment. For more information, see Sharing data between a calling flow and a response flow.

Kafka node enhancements

Message key support in the KafkaConsumer and KafkaProducer nodes

The KafkaConsumer node and KafkaProducer node have been enhanced to include support for the key environment variable, which you can use to associate a string value with a message when it is published. If a message is published to a topic with multiple partitions, the key value can be used to select the partition on which the message is stored. All messages published using the same key value are sent to the same partition. If no key is provided, messages are distributed across the topic partitions by Kafka.

For more information, see Processing Kafka messages and Using local environment variables with Kafka nodes.

REST node enhancements

User context support in the RESTAsyncRequest and RESTAsyncResponse nodes

You can share data between flows that contain RESTAsyncRequest and RESTAsyncResponse nodes, by storing and retrieving data in the UserContext folder in the local environment. You specify the context data to be stored by the RESTAsyncRequest node, and this data can later be accessed by the RESTAsyncResponse node.

For more information, see Using local environment variables with REST nodes.

Graphical mapping enhancements

Working with JSON data and REST APIs

The JSON schema keyword "allOf", which is used for combining schema type definitions, is fully supported in JSON schema files and REST API Swagger documents referenced from a message map. For more information, see Creating or transforming a JSON message by using a JSON schema.

The support for JSON schema keywords "anyOf" and "oneOf", which are used for combining schema type definitions in JSON schema files and REST API Swagger documents, has been extended. For more information, see Casting with JSON schema types and JSON schema requirements for message maps.

Fix pack V10.0.0.7 enhancements

For details of the new features in IBM Integration Bus Version 10.0 fix pack V10.0.0.7, see the following sections:

Connectivity with Kafka clusters

Connectivity between IBM Integration Bus and Kafka clusters
Two built-in nodes are provided for processing Kafka messages:
  • KafkaConsumer node, which subscribes to a Kafka topic and propagates the feed of published messages to nodes connected downstream in the flow.
  • KafkaProducer node, which publishes messages to a Kafka topic.

For more information, see Processing Kafka messages.

Fix pack V10.0.0.6 enhancements

For details of the new features in IBM Integration Bus Version 10.0 fix pack V10.0.0.6, see the following sections:

REST API connectivity

Connectivity between IBM Integration Bus and external REST APIs

A set of REST request and response nodes are provided, enabling you to interact with external REST APIs. You can use the RESTRequest node to issue synchronous requests to external REST APIs. Alternatively, you can use the RESTAsyncRequest node with the RESTAsyncResponse node to construct a pair of message flows that interact asynchronously with an external REST API. For more information, see Connecting to external REST APIs.

Graphical mapping

Working with JSON data and REST
JSON schema and REST Swagger documents are now supported by the Mapping node with the following enhancements:
  • The documents are accessible in more containers, including Applications.
  • Both JSON and YAML formats are supported.
For more information, see Creating or transforming a JSON message by using a JSON schema.

Additionally, JSON types from both JSON schema and REST Swagger documents are available for performing mapping casts, enabling you to work with REST request nodes that place data in the environment tree. For more information, see Casting elements in a message map.

LoopBack connectivity

Connectivity between IBM Integration Bus and external systems through LoopBack® connectors

You can use the LoopBackRequest node to create, retrieve, update, and delete data records in external systems, through LoopBack connectors that you have downloaded separately, such as MongoDB, Cloudant®, and PostgreSQL.

You can download and install external LoopBack connectors by using the npm tool that is provided with IBM Integration Bus, and then use the LoopBackRequest node to issue CRUD requests through the LoopBack connectors. For more information, see Working with LoopBack connectors.

Platforms and environments

Increased support for the integration node HTTP listener

You can deploy REST APIs to integration servers that are configured to use the integration node HTTP listener. For more information, see Packaging and deploying a REST API.

You can also enable Cross-Origin Resource Sharing (CORS) on the integration node HTTP listener. For more information, see Permitting web browsers to access deployed HTTP services by enabling Cross-Origin Resource Sharing.

Logging

Performance logging of the integration node HTTP listener
Parameters are added to the mqsichangeproperties command to enable performance logging of the integration node HTTP listener.
For more information, see Integration node HTTP listener parameters.

Fix pack V10.0.0.5 enhancements

For details of the new features in IBM Integration Bus Version 10.0 fix pack V10.0.0.5, see the following sections:

Simplicity and productivity

Pushing REST API definitions to IBM API Connect

When you have created and deployed a REST API, you can push (export) the REST API definition to IBM API Connect or IBM API Management. You can push one or more REST APIs to IBM API Connect, by using either the IBM Integration Bus web user interface or the mqsipushapis command. Alternatively, you can push a single REST API to IBM API Connect or IBM API Management, by using the IBM Integration Toolkit. For more information, see Pushing REST APIs to IBM API Connect or IBM API Management.

Security

Securing MQTT connections
The connection between MQTT nodes in a message flow and the MQTT server can be encrypted by using SSL. You can configure the encryption during development, during deployment, or at run time; see Securing MQTT connections.

Fix pack V10.0.0.4 enhancements

For details of the new features in IBM Integration Bus Version 10.0 fix pack V10.0.0.4, see the following sections:

Simplicity and productivity

LDAP authentication for the web user interface

You can configure the web user interface to use LDAP for web user authentication. When the integration node is enabled to use LDAP for authentication, web user access from Integration API applications and from the IBM Integration Toolkit (when connecting remotely to the integration node) is also authenticated by using LDAP. For more information, see Enabling an integration node to use LDAP for authentication.

View message flow activity log in the web user interface

You can view the activity log entries that are associated with a specific message flow, by selecting the message flow in the web user interface, and clicking the Activity Log tab. For more information, see Viewing Activity Logs for message flows.

Develop integration solutions by using REST APIs
You can now create REST APIs from scratch by using the REST API editor in the IBM Integration Toolkit to define the models, resources, and operations, or you can import a Swagger document that describes the resources and operations that you want in the REST API.

For more information about REST APIs, see Developing integration solutions by using REST APIs.

Graphical mapping

Implementing a REST API operation using message maps

You can create a message map that implements a REST API operation, by using the new option Message map with the input and output for the REST API operation operation-name. When you select this option, the map is fully populated with REST API parameters and request/response models. For more information, see Implementing a REST API operation by using a message map.

Mapping using a model defined in JSON schema
When you create a message map in one of the supported containers, the model can now be taken from either of the following sources:
  • Model definitions from a Swagger document in a REST API project
  • JSON data types in a well formed JSON schema in a shared library

For more information, see Creating or transforming a JSON output message by using a JSON schema.

Additional mapping functions for use in the Custom XPath transform
The following additional mapping functions have been provided for use in the Custom XPath transform:
  • iib:hexBinaryValue($<var> ) To set an output hex binary or BLOB value
  • iib:base64BinaryValue( $<var> ) To set an output base 64 binary value
  • iib:uuidValue() To set a new UUID value

For more information, see Custom XPath.

High performance and scalability

Splitting message flow processing between different locations

Your message flow might complete lots of different actions. If any of those actions are labor-intensive, you can split them from the main flow into a callable flow and complete them somewhere else. Callable flows also facilitate reuse because they can be called by multiple message flows. You can split your message flows between different applications in the same integration server, or between different integration servers, which can be in different integration nodes. Flows that are split between integration servers communicate securely by using a data router and connectivity agents.

For more information, see Callable message flows.

Optimization of global cache

You can configure your embedded global cache to use different locking strategies for different cache maps, and you can configure the use of replica shards of a cache map for read access. For more information, see Optimizing the embedded global cache for use with different types of cache data.

Cloud connectivity

Connectivity between IBM Integration Bus and Salesforce.com

You can use the SalesforceRequest node to make synchronous requests to Salesforce.com, to create, retrieve, update, and delete Salesforce records. The SalesforceRequest node uses an IBM loopback connector to connect to Salesforce.com and to manage the interactions. Salesforce message models are provided, which allow you to map message data in your flow. The message models are in the form of JSON schema. For more information, see Working with Salesforce.

Fix pack V10.0.0.3 enhancements

For details of the new features in IBM Integration Bus Version 10.0 fix pack V10.0.0.3, see the following sections:

Simplicity and productivity

Global transaction support with CICS® extended to z/OS® integration nodes

You can now configure CICSRequest nodes so that any recoverable work is done under a global transaction, coordinated by Resource Recovery Service (RRS). This extends the support introduced in V10.0.0.2 for integration nodes on distributed systems.

For more information, see CICSRequest node and Configuring the CICSRequest node for global transactions on z/OS.

Graphical mapping

Support for Oracle stored procedures

In previous releases, you can use a Database Routine transform to call a stored procedure from only a IBM DB2® database. In IBM Integration Bus Version 10.0 fix pack 3, support for stored procedures is extended so that you can also call a stored procedure from an Oracle database. For information about the support for stored procedures, see Support for stored procedures.

Dynamic and intelligent

Business transaction monitoring
Typically, a business transaction consists of several system-level transactions. When you monitor business transactions in IBM Integration Bus, you track and report the lifecycle of a payload message through an end-to-end enterprise transaction. To monitor business transactions, you create a business transaction monitoring definition in the web user interface.

For more information, see Business transaction monitoring.

Platforms and environments

Support for Linux® on POWER® Little Endian
You can install IBM Integration Bus on a Linux on POWER Little Endian system, but the following message flow nodes are not supported on this platform:
  • WebSphere® Adapters nodes:
    • SAPInput node
    • SAPRequest node
    • SAPReply node
    • SiebelInput node
    • SiebelRequest node
    • PeopleSoftInput node
    • PeopleSoftRequest node
    • JDEdwardsRequest node
    • JDEdwardsInput node
  • WebSphere MQ File Transfer Edition nodes:
    • FTEInput node
    • FTEOutput node
  • DecisionService node
  • IMSRequest node

IBM Integration Bus does not include any database drivers that can be used with the Linux on POWER Little Endian platform. For details about third-party database drivers that are supported, see IBM Integration Bus system requirements web page.

Fix pack V10.0.0.2 enhancements

For details of the new features in IBM Integration Bus Version 10.0 fix pack V10.0.0.2, see the following sections:

Simplicity and productivity

Global transaction support with CICS

On distributed systems, you can configure the CICSRequest node for globally-coordinated (two-phase commit) transactions.

For more information, see CICSRequest node and Configuring the CICSRequest node for global transactions on distributed systems.

Developer integration with IBM API Management
When you have created and deployed a REST API, you can push (export) the API to an IBM API Management server. You can then use the IBM API Management server to perform the following tasks:
  • Promote and monitor the usage of the REST API.
  • Secure and authenticate access requests from external users and applications to your IBM Integration Bus application.
Note: In IBM Integration Bus Version 10.0.0.2, integration is supported only with IBM API Management On-premise.
For more information, see Pushing a REST API to IBM API Management or IBM API Connect by using the IBM Integration Toolkit.

Support for WebSphere eXtreme Scale enterprise data grids

The embedded global cache can use a WebSphere eXtreme Scale enterprise data grid. Enterprise data grids use the eXtreme data format (XDF) instead of Java object serialization. XDF allows for class evolution. With class evolution, you can evolve the class definitions that are used in the data grid without affecting older applications that are using previous versions of the class. For more information, see Enterprise data grid overview in the WebSphere eXtreme Scale product documentation. To enable the use of an enterprise data grid, an integration node must meet the following requirements:

  • Integration node must be at IBM Integration Bus Version 10.0.0.2 or later.
  • Integration node must have a function level set to 10.0.0.2 or later.

For information about checking and setting function levels, see Changing the function level of your integration nodes.

Warning: If you have a multiple integration node cache topology, either all integration nodes must be configured to use the enterprise data grid, or all integration nodes must be configured to not use the enterprise data grid. If you have a multiple integration node cache topology, you must enable the enterprise data grid at the same time across all the integration nodes that are using the global cache. Complete the steps in the following order:
  1. Install IBM Integration Bus Version 10.0.0.2 (or later) on all the integration nodes that use the global cache.
  2. Stop all the integration nodes.
  3. Set the function level of all the integration nodes to 10.0.0.2 or later.
  4. Restart all the integration nodes.

For more information about using the global cache, see Managing data caching.

Graphical mapping

Cache transforms

You can use Cache transforms in a Mapping node to interact with data that is stored in a global cache. You can add a key-value pair to the cache, get a value (that is associated with a specified key) from the cache, and remove a key-value pair from the cache. For more information, see Accessing the global cache by using a Mapping node.

Platforms and environments

Extended interoperability between IBM Integration Bus and external WebSphere eXtreme Scale grids

In addition to communicating with WebSphere eXtreme Scale external grids that use the Object Request Broker (ORB) transport mechanism, IBM Integration Bus can now communicate with external grids that use the IBM eXtremeIO (XIO) transport mechanism. You do not need to configure integration nodes to enable or select a transport mechanism; the transport mechanism that is used is determined by the WebSphere eXtreme Scale external grid.

For more information, see Connecting to external WebSphere eXtreme Scale grids.

WebSphere ESB conversion tool enhancements
A built-in converter for conversion of one-way asynchronous import bindings is included:
Automatic conversion of the following entities is supported:
  • Input Fault, Callout Fault, and Error Input primitives
  • Error flows
  • Maps and paths to all contexts

For more information, see The WebSphere ESB conversion tool.

For information about installing or updating the WebSphere ESB conversion tool, see Installing or updating the WebSphere ESB conversion tool.

Troubleshooting and support

New service trace option and examples

In addition to the safe and fast modes available for user trace, there is a third mode temp that is available with integration server service trace only. This mode is the same as safe mode, but trace is automatically switched off when the component restarts. You can also specify up to 10 BIP numbers to stop the trace automatically.

For examples and more information about this mqsichangetrace option, see mqsichangetrace command - Windows, Linux, and UNIX systems

Fix pack V10.0.0.1 enhancements

For details of the new features in IBM Integration Bus Version 10.0 fix pack V10.0.0.1, see the following sections:

Simplicity and productivity

Install only the IBM Integration Bus runtime component
By default, both the IBM Integration Toolkit and the IBM Integration Bus runtime component are installed when you install IBM Integration Bus. However, you can choose to not install the IBM Integration Toolkit; see Installing IBM Integration Bus on Windows and Installing IBM Integration Bus on Linux.

Platforms and environments

Increased support for JDBC drivers

Any JDBC provider is supported, therefore if a JDBC provider is not listed in the supported database table, IBM Integration Bus provides limited support. This support has the following restrictions: The driver must be a JDBC Type 4 (Pure Java) driver. Global transaction coordination (XA) is not supported. Discoverability in the Graphical Data Mapper is not supported, and the automatic determination of field types in Graphical Data Maps is supported only if the driver correctly and fully implements java.sql.PreparedStatement.getParameterMetaData(). For more information about the field types, see Data type considerations for mapping database content.

For more information about supported JDBC drivers, see the IBM Integration Bus system requirements: http://www.ibm.com/software/integration/wbimessagebroker/requirements/

WebSphere ESB conversion tool enhancements
Automatic conversion of the following entities is supported:
  • Submaps
  • Maps and paths to transient context, shared context, and correlation context

For more information, see The WebSphere ESB conversion tool.

For information about installing or updating the WebSphere ESB conversion tool, see Installing or updating the WebSphere ESB conversion tool.