Broker 10.5 | webMethods Broker Documentation | webMethods Broker Client C API Programmer's Guide | Subscribing to and Receiving Events | Event Subscriptions
 
Event Subscriptions
 
Limits on Subscriptions
Subscribing to Events
Cancelling a Subscription
Using Wildcards
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.
Note:
You do not have to register any event subscriptions to receive a delivered event. For more information on delivering events, see Delivering Events.
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.
Note:
Event types are defined with Software AG Designer, described in the Software AG Designer Online Help . Note that event types are known as document types in Designer.
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.