Exploring IBM App Connect Enterprise 12.0.10.0

[DZone]

We'll explore seven of the features released in IBM App Connect Enterprise 12.0.10.0 and provide a high-level overview of each; 

1. Toolkit:
   • Simple JSON Mapping within the Discovery Connector Request nodes.
   • New button to open workspace file system location.
2. WebUI:
   • New Record and Replay views with Hex and Base64 encoding.
   • Resource Manager views.
3. New Change Data Capture node for integrating with PostgreSQL and DB2.
4. Built-in ODBC driver for integration with PostgreSQL databases.
5. Importing and exporting credentials using the mqsivault command.
6. Configuring an Integration Server's JRE - Java 11 changes.
7. Open Telemetry platform support extended to include AIX and pLinux.

Toolkit

Simple JSON Mapping Within the Discovery Connector Request Nodes

For the last few mod releases of App Connect Enterprise, we have rapidly expanded the number of available Discovery Connector message flow nodes - both input nodes to trigger a message flow and also mid-flow request nodes. In total, the Toolkit now provides 86 such nodes.
To further improve the usability for developers wanting to integrate with application endpoints, we have also provided an easy way to map between data structures. App Connect Enterprise 12.0.10.0 introduces the concept of executing mapping logic as part of a Discovery Connector node. This is done using the JSONata expression language capabilities which were first made available as part of the web browser-based Designer authoring experience. For more information about JSONata, which itself is an open-source technology, check out the website here, which also includes a JSONata exerciser.

To demonstrate this new Toolkit message flow capability, consider a simple scenario of triggering a flow when a GitHub issue is created and then writing a message to a Slack channel. Previously, a scenario like this one would have required an intervening message flow node such as a Compute node, JavaCompute node, or Graphical Data Map node between the GitHub Input and the Slack Request nodes, but now we can wire the nodes together directly, and apply the mapping task as part of the Slack Request node:

View the full article