Event Endpoint Management continues to be enhanced

Event Endpoint Management continues to be available and enhanced as part of IBM's integration platforms.

End of Marketing announcement for IBM Event Automation

Event Streams and Event Processing are deprecated and no enhancements will be provided. Support and security fixes will be provided in line with published support lifecycle policies. Future event-driven solutions that make use of Apache Kafka and Apache Flink will be delivered by IBM Confluent.

For more information, see how you can plan your transition.

Reverting nodes to an earlier implementation

Event Processing 1.5.5 icon In Event Processing 1.5.5 and later, the implementation of API, watsonx.ai, and deduplicate nodes has been enhanced. When you use the Event Processing UI, new flows and existing flows are automatically updated to use the new implementations.

If you encounter issues with the new implementation, you can revert individual nodes to the earlier implementation by editing the flow JSON.

Reverting a node to the earlier implementation

To revert a node to the earlier implementation, complete the following steps:

  1. Export the flow in JSON format.
  2. Open the exported file in a text editor and locate the node that you want to revert.
  3. Set the property for the node type to false:
    • For API and watsonx.ai nodes, set "useApacheConnector": false.
    • For deduplicate nodes, set "useSqlDeduplication": false.

    If the property is not present, add it to the node object.

  4. Save the file and import the updated flow into Event Processing.

Note: To restore a node to the new implementation, set the property back to true.