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 the support lifecycle transition and software ordering completion announcement.

Attention: This version of Event Endpoint Management has reached End of Support. For more information about supported versions, see the support matrix.

Redaction fails for nested fields

Symptoms

The redaction control fails to work with a property that uses a JSON path with more than one field name. For example $.person.name.

A Kafka consumer set up to consume from this option will have connection failures. The Event Gateway displays errors in the logs similar to the following example:

WARN  com.ibm.ei.gateway.eem.core.RecordDataUtils - [encodeAvro:143] The data does not match the schema: Schema with encoding: AVRO_BINARY
java.lang.ClassCastException:

...

ERROR com.ibm.ei.gateway.eem.egress.interceptors.FetchResponseRedactor (Redaction Fetch Response Interceptor) - [lambda$intercept$5:169] 
java.util.NoSuchElementException: No value present

Causes

When the Event Gateway tries to encode the message after performing the redaction, it fails to generate the nested fields correctly, and fails to create the redacted message. When the redaction failure occurs, the Event Gateway sends a null message to avoid passing on any sensitive information.

Resolving the problem

To resolve the problem, upgrade your Event Endpoint Management instance to version 11.1.3 or later.