Deploying a Subscription Management Interface
Subscription management interfaces are used to add, delete, or modify subscriber and subscription data. The interface can be a Web application, a Microsoft Windows application, or scripts.
Subscription management interfaces operate externally to Notification Services. However, these interfaces must use the subscription management objects in the Microsoft.SqlServer.NotificationServices namespace to manage subscriber and subscription data.
The exact steps for deploying a subscription management application depend on the implementation, the operating system, and the location of the instance and application databases.
Basic Deployment Steps
The following list shows the basic steps for deploying a subscription management interface. For step-by-step instructions, see "Deployment Procedures" below.
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 Notification Services client components.
- Install the subscription management interface.
- Register the instance of Notification Services so the subscription management objects can access the databases.
- Grant database permissions by adding the interface's database user account to the NSSubscriberAdmin database role in instance and application databases.
Configuring Database Access for an ASP.NET Application
If you use an ASP.NET application to manage subscriptions, it must be able to login to the SQL Server Database Engine and have the proper permissions in instance and application databases. The application can use either Windows Authentication or Microsoft SQL Server Authentication. Windows Authentication is recommended.
If using Windows Authentication, the account used depends on the ASP.NET application location, security configuration, and operating system:
- If the subscription management application is located on the same server as the databases, use the account the ASP.NET application runs under. On Microsoft Windows XP and Microsoft Windows 2000, ASP.NET applications run under the ASPNET user account. On Microsoft Windows Server 2003, ASP.NET applications run under the NT AUTHORITY\NETWORK SERVICE account.
- If the subscription management application is located on a separate server from the databases, the local ASPNET and NETWORK SERVICE accounts cannot be used. Instead, you can configure your ASP.NET application to run in the context of a domain user account.
If you cannot use Windows Authentication, you can configure a SQL Server login account for your ASP.NET application. Microsoft recommends Windows Authentication.
This section includes three walkthroughs of how to deploy subscription management applications. Use these walkthroughs to become familiar with deploying subscription management applications and to create your own instructions and batch files for deployment.
- Walkthrough: Subscription Management Interface Deployment on the Database Server
- Walkthrough: Subscription Management Interface Deployment on a Remote Server
The following topic contains procedures for the deployment steps listed above.
To install Notification Services
To register an instance of Notification Services
- How to: Register an Instance of Notification Services for Client Components (SQL Server Management Studio)
- nscontrol register Command