In order for your application to be able to receive and process events, it must first create a BrokerClient, as described in Creating and Destroying Broker Clients. Then, any event that is permitted by the client group to which the BrokerClient belongs may be retrieved by your application.

To receive published events, your application must first use the BrokerClient to subscribe to the event types that it wishes to receive. Event subscriptions are always made within the context of a particular BrokerClient.

A single BrokerClient may make multiple subscription requests, so subscriptions are distinguished by the unique combination of the event type name and an optional filter. Filters, covered in Managing Event Types, allow you to receive only those events that contain certain data in which you are interested. If your BrokerClient wishes to make two subscriptions for the same event type name, a different filter must be specified for each subscription.