IBM Integration Bus, Version 10.0.0.2 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS


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 that is added in fix packs.

For detailed information about the contents of fix packs and other maintenance packs, see the WebSphere® Message Broker support web page, which contains information about WebSphere Message Broker and IBM Integration Bus. Under the Downloads heading, click Recommended fixes and select your product to view available fixes. The description of each fix pack includes a link to Problems fixed (a list of APARs that are included).

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-premises cloud.
For more information, see Pushing a REST API to an IBM API Management server.

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.


bb23851_.htm | Last updated 2015-09-24 12:53:35