Controlling Instance and Application Operation
When you define a Notification Services application, you specify the server that runs each hosted event provider, generator, and distributor. The Notification Services engine, which can hosted by the NS$instanceName Microsoft Windows Service or by a custom application, runs these components.
When you start the Notification Services engine on a server, the engine checks the instance database and application databases to determine which components run on that server and whether those components are enabled or disabled. All enabled components start processing data. All disabled components are paused and do not process data until enabled.
This section discusses how to configure a Windows service that runs the Notification Services engine; how to start and stop instances of Notification Services; how to enable or disable instances, individual applications, or individual components of an application; and how to check the current status of instances, applications, and components.
In This Section
| Topic | Description |
|---|---|
Describes how to configure Windows service startup and restart for an instance of Notification Services. |
|
Provides information about and instructions for starting and stopping instances of Notification Services. |
|
Enabling and Disabling Instances, Applications, or Components |
Provides information about and instructions for enabling and disabling instances, applications, and parts of applications. |
Viewing the Status of Instances, Applications, and Components |
Explains how to obtain information about the status of the instance's Windows services and components and describes the status results. |
See Also
Concepts
Securing Notification Services
Hosting the Notification Services Engine
Other Resources
Administering Notification Services