This topic has not yet been rated - Rate this topic

Deploying a Non-Hosted Event Provider

SQL Server 2005

Non-hosted event providers operate externally to Notification Services; the Notification Services engine does not host them. A non-hosted event provider can be any external application that uses the event collection APIs to submit events to an instance of Notification Services. For example, the application can be a Microsoft Windows application, a script, or a Web service.

Even though the application operates externally to Notification Services, the event collection API uses information in the Windows registry to access the instance and application databases. For this reason, you must register the instance of Notification Services on the computer that runs the non-hosted event provider.

You also must configure database permissions for the account used by the non-hosted event provider. Non-hosted event providers must be a member of, or have at least the permissions of, the NSEventProvider database role in the instance and application databases.

Basic Deployment Steps

The following list shows the basic steps for deploying a non-hosted event provider. For step-by-step instructions, see "Deployment Procedures" below.

Important:
In Microsoft SQL Server 2005, network protocols are disabled by default. If any Notification Services components are running on a server other than the database server, you must enable the appropriate network protocol. For more information, see SQL Server Surface Area Configuration.

Install the non-hosted event provider application according to the instructions provided by the application developer.
Install the Notification Services client components.
Register the instance of Notification Services.
Grant Microsoft SQL Server access and database permissions to the account used by the non-hosted event provider.

Walkthroughs

This section includes a walkthrough of how to deploy non-hosted event providers using Windows Authentication. Use the walkthroughs to become familiar with deploying non-hosted event providers and to create your own instructions and batch files for deployment.