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).
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.
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.
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.
For more information about REST APIs, see Developing integration solutions by using REST APIs.
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.
For more information, see Creating or transforming a JSON output message by using a JSON schema.
For more information, see Custom XPath.
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.
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.
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.
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.
In previous releases, you can use a Database Routine transform to call a stored procedure from only a 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.
For more information, see Business transaction monitoring.
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.
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.