Module 13 Notification Services

What is it?

Notification Services notifies subscribers of the occurrence of events

Makes use of two different types of databases, application databases and instance databases which are configured with XML files. The config file configures the instance database and an application definition file which configures the application database.

Each instance of Notification Services has it’s own process.

Subscribers subscribe to the notifications made available by the application by using a subscription management application. This is using managed code.

Architecture

Physical:Instances

-Defined by config files

-Implemented as a windows service

-can contain one or more applications

-service and database are defined in config files.

-the application database is defined in and Application Definition File (ADF)

Physical Applications

-Each app defined with ADF

-each app has separate DB

Logical

-Each solution requires a NS Instance

-instance contains one or more applications

Notification Generation

One quanta per ADF file, defines the interval in which the generator is going to run.

Notification Formatting and delivery

Can subscribe in digest.

Multicast = one to several subs

Trigger can be an event provider

Dev Process

-design solution

-config ADF files

-register and build application

-create sub management application

-implement an event provider (i.e. trigger)

Config and Instance

-Parameters

-Documentation (vss)

-instance settings (name,which sql server instance)

-application settings (not just ADF configured here too)

-protocol settings (optional)

-delivery channels

-argument encryption

Demo: Looking at a ADF configuration file (XML) D:\Practices\Config.xml

Defining Event Providers

Event Providers:

Standard providers

FileSystemWatcher

SQL Server

Custom Provider APIs

Managed event API

COM event API

XML event API

SQL Server event API