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).
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.
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:
For information about checking and setting function levels, see Changing the function level of your integration nodes.
For more information about using the global cache, see Managing data caching.
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.
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.
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.
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
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/
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.