Find out what is new in Event Endpoint Management version 11.8.0.
Release 11.8.0
Terminology changes
Event Endpoint Management release 11.8.0 contains the following terminology changes:
- Options are now called Virtual topics. Previously, the term options was used for event endpoints from the perspective of authors (Kafka administrators). To avoid confusion, the same term is now used for event endpoints from all perspectives.
- Event endpoints are now called Virtual topics. Previously, the term event endpoints was used for options that were published to the catalog.
- Event sources are now called topics, or source topics in places where confusion with virtual topics is possible.
Multiple topic subscriptions: applications
Users can now subscribe to multiple virtual topics with the same credentials by using a new feature called applications. Applications allow clients to access multiple virtual topics with the same credentials.
Existing subscriptions are converted to applications that subscribe to the same virtual topic and use the same credentials.
Important: To enable applications to subscribe to multiple topics, you must convert your existing gateways to provide new prerequisite configuration values.
Content filtering
You can now use content filtering to control which events are delivered to subscribers. Define filters based on event data or subscriber data to ensure that only relevant events are delivered.
IBM API Connect Developer Portal integration
Event Endpoint Management 11.8.0 introduces an integration with IBM API Connect Developer Portal v12.1.1 or later. You can now publish virtual topics to Developer Portal in addition to the Event Endpoint Management catalog.
Event Gateway deployment and configuration enhancements
In Event Endpoint Management 11.8.0 and later, the Event Endpoint Management operator can deploy the Event Gateway without requiring users to create a configuration in the Event Endpoint Management UI beforehand.
Event Gateway configuration procedures are updated to suit the gateway deployment type: operator-managed gateways are configured in the custom resource, Kubernetes Deployment gateways are configured with a ConfigMap. For more details, see gateway properties reference.