IBM Integration Bus, Version 10.0.0.5 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.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

Start of changeWhen 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.End of change

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


bb23851_.htm | Last updated 2016-06-25 08:08:24