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 Flink will be delivered by IBM Confluent Platform.

For more information, see the support lifecycle transition and software ordering completion announcement.

Configuring a client application to connect to an event endpoint

Configure your client applications to connect to the Event Gateway to access your subscriptions.

Use the code snippets provided for each event endpoint, along with your subscription details.

Configuring a client application to connect to an event endpoint.

Configuring a client

The Event Gateway manages access to event endpoints in Event Endpoint Management. Configure your client applications to connect to the Event Gateway by using standard Kafka client configuration options.

The way that you provide the configuration settings to your client varies from client to client. However, the following settings are common for every client:

  • Bootstrap servers: The set of Event Gateway Server addresses that provide access to an event endpoint can be found in the Catalog page for that event endpoint, in the Server table. If multiple addresses are used, separate them with commas.
  • Security mechanism: Set as SASL_SSL if username and password are used in the subscription. Set as SSL if mTLS is used without a username and password.
  • SSL configuration: The Event Gateway exposes only a TLS-secured endpoint for clients to connect to. For each Gateway endpoint address, the server certificate can be downloaded (in PEM format) from the Catalog detail page. Configure your client to trust this certificate.
  • SASL credentials : If SASL_SSL is specified as the SASL mechanism, then set SASL username, and SASL password with the values retrieved when you subscribed to the event source.
  • Topic name: The name of the event endpoint you want your application to use. The name is displayed in the Catalog table under the Topic name column and as the heading of the Catalog detail page when you view more information about an event endpoint.