microsoft.public.sqlserver.notificationsvcs
[Top] [All Lists]

Re: Delivery Channels and Protocols

Subject: Re: Delivery Channels and Protocols
From: Joe Webb
Date: Thu, 01 Sep 2005 10:21:12 -0500
Newsgroups: microsoft.public.sqlserver.notificationsvcs
Andy - 

Have you tried changing the device names to something unique like
"mobileemail" and "desktopemail"?



-- 
Joe Webb
SQL Server MVP


~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811 

I support PASS, the Professional Association for SQL Server.
(www.sqlpass.org)


On Thu, 1 Sep 2005 07:26:46 -0400, "Andy" <[email protected]>
wrote:

>I tried to see if I put a folder for the channel name to see if the XSLT 
>would be found, it was not. It is only based on the DeviceName, in my case 
>SMTP.
>
>I will find a solution, just wanted to make sure I was not missing 
>something. I will probably create a custom component.
>
>
>"Joe Webb" <[email protected]> wrote in message 
>news:[email protected]
>> Andy -
>>
>> I gotta agree with Kate on this. I think the built in SMTP protocol
>> should do what you're after if you define a different XSLT template
>> for each device type.
>>
>> For example you could send emails to a cellphone formatted one way and
>> to a computer formatted another.
>>
>> Maybe I'm misunderstanding what you're trying to do?
>>
>> HTH...
>>
>> -- 
>> Joe Webb
>> SQL Server MVP
>>
>>
>> ~~~
>> Get up to speed quickly with SQLNS
>> http://www.amazon.com/exec/obidos/tg/detail/-/0972688811
>>
>> I support PASS, the Professional Association for SQL Server.
>> (www.sqlpass.org)
>>
>>
>> On Mon, 29 Aug 2005 08:41:17 -0400, "Andy" <[email protected]>
>> wrote:
>>
>>>You are somewhat following what I am trying to get across, but still it 
>>>does
>>>not work, from what I read. I will try to test it in the next couple of
>>>weeks myself and report back if it does work.
>>>
>>>
>>>
>>>What I read is that the XSLTFormatter is based on DeviceName, such as out 
>>>of
>>>the box SMTP. If I want to send different versions of the message via SMTP 
>>>I
>>>cannot do that unless I decide to fake things out using locale.
>>>
>>>
>>>
>>>I want to be able to send messages to two SMTP recipients without writing 
>>>a
>>>custom component.
>>>
>>>
>>>
>>>It just seems to be the XSLTFormatter should base its logic on the Channel
>>>Name rather than specific device type. This allows you to have multiple
>>>formats going out via the same protocol, SMTP, without having to build a
>>>similar component to do the job.
>>>
>>>
>>>
>>>From my prior post let's walk through the logic, again maybe I am missing
>>>something and it will work the way I want it too already:
>>>
>>>
>>>
>>>I have a subscriber that wants to have notifications sent to both regular
>>>email and a mobile device, which is restricted to amount of text it can
>>>receive. So I would hope to define the following in the ICF:
>>>
>>>
>>>
>>><DeliveryChannel>
>>>   <DeliveryChannelName>SMTPChannel</DeliveryChannelName>
>>>   <ProtocolName>SMTP</ProtocolName>
>>>   <Arguments>
>>>      <Argument>
>>>         <Name>SmtpServer</Name>
>>>         <Value></Value>
>>>      </Argument>
>>>      <Argument>
>>>         <Name>Bod oding</Name>
>>>         <Value>utf-8</Value>
>>>      </Argument>
>>>   </Arguments>
>>></DeliveryChannel>
>>><DeliveryChannel>
>>>   <DeliveryChannelName>MobileSMTPChannel</DeliveryChannelName>
>>>   <ProtocolName>SMTP</ProtocolName>
>>>   <Arguments>
>>>      <Argument>
>>>         <Name>SmtpServer</Name>
>>>         <Value></Value>
>>>      </Argument>
>>>      <Argument>
>>>         <Name>Bod oding</Name>
>>>         <Value>utf-8</Value>
>>>      </Argument>
>>>   </Arguments>
>>></DeliveryChannel>
>>>
>>>
>>>
>>>I would then create the same XSLT file, differing in how to format the
>>>message, in the path of my XSLT to match like the following:
>>>
>>><xsltpath>\MobileSMTPChannel
>>>
>>><xsltpath>\SMTPChannel
>>>
>>>
>>>
>>>From what I know this is not handled by NS, but only the following is 
>>>since
>>>it is based on devicename:
>>>
>>><xsltpath>\SMTP
>>>
>>>
>>>
>>>I could fake things out by using the following:
>>>
>>><xsltpath>\SMTP <!--Will handle regular emails -->
>>>
>>><xsltpath>\fr-FR\SMTP <!-- Will handle mobile emails since we have no
>>>intention to customize to other languages, so I just chose one for this
>>>example -->
>>>
>>>
>>>
>>>Perhaps this lays out better what I hope to achieve. Again, I will test 
>>>this
>>>in the next couple of weeks, but just thought I would get help from those
>>>who have used is a lot more.
>>>
>>>
>>>"kate" <[email protected]> wrote in message
>>>news:[email protected]
>>>> hi andy
>>>>
>>>> i think what you are saying is that you want to use the existing SMTP
>>>> channel if you can for easy dev. but you need to pick up the correct
>>>> device xslt template for the notification so that the resulting output
>>>> is suitable for the end-point device.
>>>>
>>>> the NS design offers us multiple delivery channel and a protocol can be
>>>> used across one or many channels. the xslt formatter includes the
>>>> option to pick up an xslt file based on the devicetype of the channel.
>>>>
>>>> so you can have 2 deliverychannels as in your sample code which both
>>>> call the SMTP protocol although each my point to a different mail
>>>> server. define a different devicetype code for each and create a
>>>> matching xslt file suitable for the target device. the only contstraint
>>>> is that because they use the same protocol they have the same data
>>>> elements to choose from . but that shouldnt be a problem.
>>>>
>>>> so you should be able to do what you suggested.
>>>>
>>>> Kate MBCS
>>>>
>>>> Alert Technologies
>>>> http://www.alert-technologies.co.uk
>>>> Get your notification services implementation going in minutes not
>>>> weeks ......
>>>>
>>> 
>

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