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).
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/
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