IBM Integration features
Some features of IBM® Integration Bus have specific requirements, such as a specific mode of operation or the availability of an additional product, such as a database or access to WebSphere® MQ. Additional terms and conditions also apply to the use of some IBM Integration Bus features, including the requirement for other product licenses.
If you intend to use any of the IBM Integration Bus features that require MQ functionality, you can install and use WebSphere MQ within the terms of your IBM Integration Bus license. For more information about using WebSphere MQ with IBM Integration Bus, see Installing WebSphere MQ.
You can choose the mode of operation for your integration nodes based on the functionality and capacity that you require:
- In express mode, the integration node operates with a limited set of nodes for use with a single integration server.
- In scale mode, the integration node operates with a limited set of nodes for use with unlimited integration servers.
- In standard mode, the integration node operates with all features enabled but you are limited to creating only one integration server.
- In advanced mode, the integration node operates with all features enabled (apart from the SalesforceRequest node), and there is no limit to the number of integration servers or the number of message flows deployed to each integration server.
Other modes of operation are also available for use under specific conditions (developer mode, applicationIntegrationSuite mode, and adapter mode); for more information, see Operation modes.
The following table provides an overview of the main IBM Integration Bus capabilities, and shows the modes of operation in which they are available. The table also indicates where additional requirements or restrictions apply.
| Capability | Description | Express mode | Standard mode | Scale mode | Advanced mode | Application IntegrationSuite mode |
|---|---|---|---|---|---|---|
| Vertical scaling | Unlimited integration servers can be used. | No | No | Yes | Yes | Yes |
| Web Standards connectivity | The following nodes are provided:
Support is also provided for REST, XML, and JSON. |
Yes | Yes | Yes | Yes | Yes |
| REST connectivity | The following nodes are provided: | Yes | Yes | Yes | Yes | Yes |
| Kafka connectivity | The following nodes are provided: | Yes | Yes | Yes | Yes | Yes |
| Cloud connectivity | A SalesforceRequest node is provided. | No | No | No | No | Yes7 |
| An AppConnectRESTRequest node is provided. | Yes | Yes | Yes | Yes | Yes | |
| LoopBack® connectivity | A LoopBackRequest node is provided. | Yes | Yes | Yes | Yes | Yes |
| ODBC connectivity | A Database node is provided. | No | Yes | No | Yes | Yes |
| Java™ connectivity and JDBC | The following nodes are provided:
For JMSMQTransform and MQJMSTransform nodes, WebSphere MQ (Client or Server) must be installed on the same machine as the integration node. For more information, see Installing WebSphere MQ. |
Yes | Yes | Yes | Yes | Yes |
| MQ connectivity | The following nodes are provided:
Support is also provided for content-based filtering. WebSphere MQ (Client or Server) must be installed on the same machine as the integration node. For more information, see Installing WebSphere MQ. |
Yes | Yes | Yes | Yes | Yes |
| Graphical mapping and XSL | The following nodes are provided: | Yes | Yes | Yes | Yes | Yes |
| Flow control | The following nodes are provided:
Support is also provided for subflows. For timeout nodes, WebSphere MQ Server must be installed on the same machine as the integration node, and the integration node must not share a queue manager with another integration node. For more information, see Installing WebSphere MQ. |
Yes | Yes | Yes | Yes | Yes |
| Callable flows | The following nodes are provided: | Yes | Yes | Yes | Yes | Yes |
| Routing | A Route node is provided. | No | Yes | Yes | Yes | Yes |
| Email, File, and (S)FTP connectivity | The following nodes are provided: | Yes | Yes | Yes | Yes | Yes |
| User-defined logic | Support is provided for user-defined nodes, parsers, and exits. | Yes | Yes | Yes | Yes | Yes |
| BPM support | The following nodes are provided:
For MQ bindings, WebSphere MQ Server must be installed on the same machine as the integration node. For more information, see Installing WebSphere MQ. |
No | Yes | Yes | Yes | Yes |
| WSRR support | The following nodes are provided: | No | Yes | Yes | Yes | Yes |
| Microsoft .NET | The following nodes are provided: | Yes | Yes | Yes | Yes | Yes |
| Patterns technology | Support is provided for built-in and user-defined patterns technology. | Yes1 | Yes1 | Yes1 | Yes1 | Yes1 |
| Administration interfaces | The following administration interfaces are provided: | Yes | Yes | Yes | Yes | Yes |
| Record and replay | Support is provided for recording and replaying
messages. WebSphere MQ Server must be installed on the same machine as the integration node. For more information, see Installing WebSphere MQ. |
Yes2 | Yes2 | Yes2 | Yes2 | Yes2 |
| Built-in caching | An integration node-embedded cache uses WebSphere Extreme Scale technology. | Yes | Yes | Yes | Yes | Yes |
| Mobile integration | Mobile integration patterns are provided. | Yes1, 3 | Yes3 | Yes1, 3 | Yes3 | Yes3 |
| High availability | Support is provided for multi-instance integration
node. WebSphere MQ Server must be installed on the same machine as the integration node. For more information, see Installing WebSphere MQ. |
Yes4 | Yes4 | Yes4 | Yes4 | Yes4 |
| TCP/IP | The following nodes are provided: | Yes | Yes | No | Yes | Yes |
| SQL | The following nodes are provided:
Support is also provided for ODBC database and ESQL deployment. |
No | Yes | No | Yes | Yes |
| Aggregation | The following nodes are provided:
To use aggregation nodes, WebSphere MQ Server must be installed on the same machine as the integration node, and the integration node must not share a queue manager with another integration node. For more information, see Installing WebSphere MQ. |
Yes | Yes | Yes | Yes | Yes |
| Advanced data processing | The following nodes are provided:
For Collector, Sequence, and Resequence nodes, WebSphere MQ Server must be installed on the same machine as the integration node, and the integration node must not share a queue manager with another integration node. For more information, see Installing WebSphere MQ. |
No | Yes | No | Yes | Yes |
| Advanced Policy Enforcement Point (PEP) processing | A SecurityPEP node is provided. | No | Yes | No | Yes | Yes |
| Built-in application adapters | The following nodes are provided:
For transactional support with SAP nodes, WebSphere MQ Server must be installed on the same machine as the integration node. For more information, see Installing WebSphere MQ. |
No | Yes | Yes5 | Yes | Yes |
| Managed file support | The following nodes are provided:
For CD and FTE nodes, WebSphere MQ Server must be installed on the same machine as the integration node. For more information, see Installing WebSphere MQ. |
No | Yes | No | Yes | Yes |
| Business decisions | No | Yes6 | No | Yes6 | Yes6 | |
| CICS®, IMS, CORBA | The following nodes are provided: | No | Yes | No | Yes | Yes |
| MQ Telemetry Transport (MQTT) | The following nodes are provided: | Yes | Yes | Yes | Yes | Yes |
- Assets created using the patterns technology can use only the features to which you are entitled under the terms of your license.
- Record and replay capabilities require a supported database.
- Mobile integration is optimized for use with Worklight Server.
- Separate licenses are required for Warm Standby instances.
- A separate license for adapters is required before you can use the WebSphere Adapters nodes in Scale mode.
- A separate license for either IBM Decision Server or IBM Decision Server Rules Edition for Integration Bus is required before you can use the DecisionService node.
- A separate license for Application Integration Suite is required before you can use the SalesforceRequest node.