Developing Non-Hosted Event Providers
Non-hosted event providers run independently of Notification Services. They are separate applications or components that submit events to a Notification Services application.
Types of Non-Hosted Event Providers
Non-hosted event providers can be stand-alone Web, Microsoft Windows, or console applications, Transact-SQL scripts or triggers, services, or can be integrated into an existing application or service. The only constraint that Notification Services places on non-hosted event providers is that they must use the event submission APIs. For more information about these APIs, see Custom Event Providers.
Accessing Notification Services
When using the event submission APIs, you must indicate the Notification Services instance, application, and event class for the event. There are two ways to do this:
- Using the InstanceEnumeration, ApplicationEnumeration, and EventClassEnumeration classes, which are included in the Notification Services API to programmatically select the appropriate instance, application, and event class names at run time.
- Using the instance, application, and event class names to initialize objects and as parameters to API methods. We recommend this approach if your application accesses only one Notification Services application.
Using Non-Hosted Event Providers
To use a hosted event provider, you must declare it in the application definition. For more information, see Defining Non-Hosted Event Providers.
See Also
Concepts
Using the Managed Event Submission API
Using the XML Event Loader API
Using Event Submission Stored Procedures
Other Resources
Developing a Custom Event Provider
Defining Event Providers