IBM App Connect Enterprise features
Some features of IBM® App Connect Enterprise have specific requirements, such as a specific mode of operation or the availability of an additional product, such as a database or access to IBM MQ. Additional terms and conditions also apply to the use of some IBM App Connect Enterprise features, including the requirement for other product licenses.
If you intend to use any of the IBM App Connect Enterprise features that require MQ functionality, you can install and use IBM MQ in conjunction with App Connect Enterprise, within the terms of your IBM App Connect Enterprise license. For more information about using IBM MQ with IBM App Connect Enterprise, see Installing IBM MQ.
You can choose the mode of operation for your installation of App Connect Enterprise, based on the functionality and capacity that you require:
- In advanced mode, all features are enabled and there is no limit to the number of integration servers or the number of message flows deployed to each integration server.
- In standard mode, all features are enabled but you are limited to creating only one integration server.
You can also choose to run App Connect Enterprise in developer mode, in which all features are enabled, but you can use the product for evaluation, development, and test purposes only. Developer Edition is limited to one message (transaction) per second at the message flow level. For more information, see Operation modes.
| Capability | Description |
|---|---|
| Vertical scaling | Unlimited integration servers can be used. |
| Web Standards connectivity | The following nodes are provided:
Support is also provided for REST, XML, and JSON. |
| REST connectivity | The following nodes are provided: |
| Kafka connectivity | The following nodes are provided: |
| Cloud connectivity | A SalesforceRequest node is provided. |
| An AppConnectRESTRequest node is provided. | |
| LoopBack® connectivity | A LoopBackRequest node is provided. |
| ODBC connectivity | A Database node is provided. |
| Java™ connectivity and JDBC | The following nodes are provided:
For JMSMQTransform and MQJMSTransform nodes, IBM MQ (Client or Server) must be installed on the same machine as the integration server. For more information, see Installing IBM MQ. |
| MQ connectivity | The following nodes are provided:
Support is also provided for content-based filtering. |
| Graphical mapping and XSL | The following nodes are provided: |
| Flow control | The following nodes are provided:
Support is also provided for subflows. Timeout nodes require access to system queues on either a local or remote IBM MQ queue manager. For more information, see Installing IBM MQ. |
| Callable flows | The following nodes are provided: |
| Routing | A Route node is provided. |
| Email, File, and (S)FTP connectivity | The following nodes are provided: |
| User-defined logic | Support is provided for user-defined nodes, parsers, and exits. |
| WSRR support | The following nodes are provided: |
| Microsoft .NET | The following nodes are provided: |
| Patterns technology | Support is provided for built-in and user-defined patterns technology. |
| Administration interfaces | The following administration interfaces are provided: |
| Record and replay | Support is provided for recording and replaying messages. Access is required to system queues on either a local or remote IBM MQ queue manager. For more information, see Installing IBM MQ. |
| Built-in caching | An integration node-embedded cache uses WebSphere Extreme Scale technology. |
| Mobile integration | Mobile integration patterns are provided. |
| High availability | Support is provided for multi-instance integration nodes. IBM MQ Server must be installed on the same machine as the integration node. For more information, see Installing IBM MQ. |
| TCP/IP | The following nodes are provided: |
| SQL | The following nodes are provided:
Support is also provided for ODBC database and ESQL deployment. |
| Aggregation | Group nodes and aggregation nodes provide alternative ways to collate related
requests and responses:
Aggregation nodes require access to system queues on either a local or remote IBM MQ queue manager. For more information, see Installing IBM MQ. |
| Advanced data processing | The following nodes are provided:
Collector, Sequence, and Resequence nodes require access to system queues on either a local or remote IBM MQ queue manager. For more information, see Installing IBM MQ. |
| Advanced Policy Enforcement Point (PEP) processing | A SecurityPEP node is provided. |
| Built-in application adapters | The following nodes are provided:
For transactional support with SAP nodes, IBM MQ Server must be installed on the same machine as IBM App Connect Enterprise. For more information, see Installing IBM MQ. |
| Managed file support | The following nodes are provided:
For CD and FTE nodes, IBM MQ Server must be installed on the same machine as IBM App Connect Enterprise. For more information, see Installing IBM MQ. |
| CICS®, IMS, CORBA | The following nodes are provided: |
| MQ Telemetry Transport (MQTT) | The following nodes are provided: |