...
set notification header values. In the stored procedure example, the headers
are treated as stored procedure parameters. For instance, if your protocol
<Field><FieldName>Foo</FieldName><FieldReference>NotificationField1</FieldReference></Field>
This posting is provided "AS IS" with no warranties, and confers no rights.
"andyjax" <andyjax@newsgroup.nospam> wrote in message
news:A6131174-1C0F-472C-BA2C-FD1629EF5EFE@microsoft.com...
>I know the general stuff BOL states, but just wanted to know if I can have
>a
> concrete of what to add where. I am just not sure what all is needed in
> each
> part.
> Primarily, what does in the adf. I have a stub, but don't think it is
> correct:
> <Protocol>
> <Fields>
> <Field><FieldName>Server</FieldName></Field>
> <Field><FieldName>Database</FieldName></Field>
> <Field><FieldName>SProc</FieldName></Field>
> <Field><FieldName>AppName</FieldName></Field>
> <Field><FieldName>CommandTimeout</FieldName></Field>
> </Fields>
> </Protocol>
>
> I have the following in the config file:
> <Protocol>
> <ProtocolName>StoredProcProtocol</ProtocolName>
> <ClassName>Landstar.Notifications.DeliveryProtocol.StoredProcProtocol</ClassName>
> <AssemblyName>c:\Projects\CustomProtocol\bin\Debug\StoredProcProtocol.dll</AssemblyName>
> </Protocol>
>
>
> I need to define the delivery channel too, from what I can tell.
>
> I really thought that since there was an example of what I needed, to call
> a
> stored proc, that all the other details would be easy enough for MS to
> provide.
>
> Thanks for the quick response. I look forward to hearing more.
>
>
> "Colin Meek" wrote:
>
>> See the article "Defining Custom Delivery Protocols" for more
>> information.
>>
>> The basic steps:
>>
>> - Add a reference to the protocol assembly in the instance configuration
>> file (ICF) or using NS Management Objects (NMO)
>> - Declare a "delivery channel" in the ICF or through NMO referencing the
>> protocol
>> - Your "NotificationClass" definition must also reference the protocol
>>
>> - Colin Meek [MSFT]
>>
>> 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
>>
http://www.microsoft.com/info/cpyright.htm. >>
>> "andyjax" <andyjax@newsgroup.nospam> wrote in message
>> news:F25AA332-75E3-4F35-8FD6-F0B7FE85CB47@microsoft.com...
>> > In looking at notification services there is an example in the SQL 2005
>> > April
>> > CTP BOL that shows how to create a stored procedure custom protocol.
>> > The
>> > only
>> > thing missing is the code to add to the config and adf.
>> >
>> > Can someone provide and example for this?
>>
>>
>>