[Top] [All Lists]

Re: Delivery Channels and Protocols

Subject: Re: Delivery Channels and Protocols
From: "Andy"
Date: Fri, 9 Sep 2005 14:54:18 -0400
Newsgroups: microsoft.public.sqlserver.notificationsvcs
I was wondering when we would get your input. Glad your back.

I believe I have finally entered my data in correctly, based on information 
both Kate and Joe gave. I guess I must have just mistyped something before, 
but it is now working.

What was done to accomplish it was to have a single deliverychannel, but 
when the device is stored give the different formats a name that applies to 
the format, so I have SMTP and MobileEmail as my two different values. I 
have created the folders to match the name and am successfully sending out 
emails with the formats needed.

Thanks for all the input.

"Shyam Pather [MSFT]" <[email protected]> wrote in message 
news:[email protected]
> I've been out of commission for a little while and I've just caught up on 
> this thread now. I'll try to explain how the device name/type/channel 
> thing works.
> The DeviceTypeName is just a string that you use to identify a particular 
> type of device in your application. You can use whatever value you 
> choose - they just have to be well understood within your application.
> DeviceTypeName is not tied to the delivery protocol name. The delivery 
> protocol name just identifies a particular protocol implementation to use. 
> This can be a built-in protocol or a custom delivery protocol.
> You configure one or more delivery channels that use the delivery 
> protocols. The delivery channels identify specific endpoints and include 
> configuration/addressing information for those endpoints.
> In your match rules, you specify the subscriber Id and device name for 
> each notification. These are used to look up the corresponding subscriber 
> device record. The device type from this record is passed, along with the 
> notification data, to the content formatter, which uses this to do 
> device-specific formatting. In the case of the XSLT formatter, this is 
> used to pick an XSLT file from an appropriately named directory.
> The delivery channel name specified in the subscriber device record 
> identifies a delivery channel. The distributor passes the formatted 
> notification data to a protocol object (of the type specified in the 
> delivery channel definition) configured to send to the endpoint that the 
> delivery channel represents.
> In short, here's how to get mails delivered using the standard SMTP 
> protocol, formatted for a variety of device types:
> -Create as many SMTP delivery channels as you have SMTP servers you send 
> to. Every subscriber device must be configured to one of these delivery 
> channel and specify some device type.
> -Create XSLTs for each device type you support and place them in the 
> appropriate subdirectories.
> -Make sure your match rules specify the right device name for each 
> notification.
> Hope this helps. All of this is explained in more detail in chapters 9 and 
> 10 of my book.
> -shyam
> Learn more about SQL-NS: 
> ---------------------------------------------
> This posting is provided "AS IS" with no warranties, and confers no 
> rights. Use of included script samples are subject to the terms specified 
> at
> ---------------------------------------------
> "Andy" <[email protected]> wrote in message 
> news:eUbPiO%[email protected]
>>I believe if I change the DeviceTypeName things will work, but I am not 
>>clear as to what that name really means. It seemed like from examples I 
>>saw that the DeviceTypeName matches the Protocol Name. I will try to see 
>>the outcome if I manually change it next week some time. I hope it was 
>>just a matter of me not interpreting the examples correctly and it will 
>>work as we need it only adding the differences in the ICF. What if the 
>>subject needs to be different between the two, how do you define that in 
>>the ADF?
>> "kate" <[email protected]> wrote in message 
>> news:[email protected]
>>> hi andy,
>>> as joe says, just change one of your devicenames to anything eg
>>> TestDevicename, and then set up a matching xslt in a folder of the same
>>> name. and give that a try.
>>> it should pick it up correctly for notifications against the
>>> subscription for the altered devicename
>>> Kate MBCS
>>> Alert Technologies
>>> Get your notification services implementation going in minutes not
>>> weeks ......
>>> .

<Prev in Thread] Current Thread [Next in Thread>