Defining Notification Services Applications
To define a Notification Services application, you either create an XML application definition file (ADF) or you define the application programmatically using Notification Services Management Objects (NMO). In either case, to define an application, you provide the following information:
-
An optional definition of the application database.
-
Event class properties, such as event class names, schemas, chronicles, and indexes.
-
Subscription class properties, such as subscription class names, schemas, rules, chronicles, and indexes.
-
Notification class properties, such as notification class names, schemas, content formatters, protocols, and delivery options.
-
Event provider properties.
-
Generator properties.
-
Distributor properties.
-
Operational settings.
-
Application version and history.
| Topic | Description |
|---|---|
|
Describes how to define the application database. | |
|
Contains topics on how to define event classes, which describe the input to an application. | |
|
Contains topics on how to define subscription classes, which describe the subscriptions users can create for an application and the rules used to generate notifications from those subscriptions. | |
|
Contains topics on how to define notification classes, which describe the notifications to be sent to subscribers. | |
|
Contains topics on how to define event providers, which are components that supply events to applications. | |
|
Describes how to define the generator location and thread pool. | |
|
Describes how to define distributor locations and operational settings. | |
|
Contains topics on how to configure run-time settings for an application. | |
|
Describes how to define the application version and history. | |
|
Describes how to specify values for ADF parameters. |
