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

Re: Accessing Notification Services using a remote client applicat

Subject: Re: Accessing Notification Services using a remote client applicat
From: Joe Webb
Date: Mon, 28 Mar 2005 10:23:19 -0600
Newsgroups: microsoft.public.sqlserver.notificationsvcs
Balaji -

That leaves a web service as your only option. Your thick client can invoke calls to a web service, passing the relevant information, and then the web service can do the SQLNS work to create the subscriptions.


HTH...
Joe Webb
SQL Server MVP

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



Balaji Ramachandran wrote:
Hi Shyam & Joe,

Thanks for your replies.

We don't want to install any client components in the client machine.

We want to go for No-touch deployment. (With this approach, you copy the files to a Web server, and the .NET Framework will automatically download the application and its dependent assemblies to the client when the user clicks a link. more info can be found in http://msdn.microsoft.com/library/en-us/dnpag/html/scag-ch07.asp?frame=true)
So installing any application in the client part is ruled out.

As the notification subscription is going to be a part of the application, our clients doesn't agree to install any components for this notification subscription module.
As the other modules uses rich GUI, it requires thick client. Hence using
ASP.Net solution for Notification subscription alone is also ruled out.
We need to design a solution with this constraints.
1.Should support no-touch deployment
2.Should use thick client.
3.Should be able to invoke notification subscriptions from all client machines.
4.No seperate installation is allowed in the client machine.

Help us out.

Thanks.

Regards,
R.Balaji




"Shyam Pather [MSFT]" wrote:


Joe's reply is correct. I just want to add one thing in answer to Balaji's
question about not wanting to use ASP.NET. All of the NS APIs are accessible
through COM-interop. So you can instantiate the NSInstance, NSApplication,
Subscriber, Subscription etc. in any application that can create COM
objects. So you can use ASP (not ASP.NET) if you like. The Books Online
describes how to do this.
Thanks
-shyam

--
Learn more about SQL-NS:
http://www.amazon.com/exec/obidos/tg/detail/-/0672326647/
---------------------------------------------
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.
---------------------------------------------
"Joe Webb" <[email protected]> wrote in message
news:[email protected]

You don't need to install everything on the client computers, just the
client components.

Here's an excerpt from BOL that explains everything.


Installing Client Components
Client components include the Notification Services API and the
NSControl commands. These components are required for:

* Subscription management applications. These applications use the
Notification Services API to interact with Notification Services
subscriber and subscription data; you must use the NSControl commands to
register the instance on the server.

* Independent event providers use the Notification Services API to
submit events to the application databases; you must use the NSControl
commands to register the instance on the server.
* Remote administration servers must have the NSControl commands so you
can administer instances and applications.


The bulk event submission subcomponent, which supports use of the
Microsoft SQLXML bulk loader, is used for submitting XML data to SQL
Server. If your independent event provider or subscription management
application submits XML data, you must install this component. However,
installing this component requires the SQL Server client tools to be
installed. Because the client tools can be used to access databases, it
is best not to install them unless necessary.


*Note*  All of the client components are included in the engine
components. If you have already installed the engine components on the
server, you do not need to install the client components.

To install the client components

1. Ensure that the client component prerequisite software is installed.
For more information, see Hardware and Software Requirements.

2. Run Notification Services Setup.

3. On the Custom Setup page, do the following:
* Click Client Components, and then select This feature will be
installed on local hard drive.

* If an application requires the SQLXML bulk loader component, click
Bulk Event Submission, and then select This feature will be installed on
local hard drive.

* Click each of the other components, and then select This feature will
not be available.

4. On the Ready to Install the Program page, click Install.


After you've installed the NS client components, you can use NSControl
on the client computer to register the server.

For the full document, look up "installing Notification Services
components" in BOL. If you have more questions after reading this, feel
free to post again.


HTH...
Joe Webb
SQL Server MVP

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



Balaji Ramachandran wrote:

Hi Joe,

Thanks for your reply.

As NSControl is installed alone with SQL server notification services,
Does

it means that all client machines who want to access the Notification
Subscription Mgmt Services needs to install the SQL notification
services?

How does the client machines which doesn't have notification services
installed access the Notification subscription management ?

In our scenario, we need to create subscription management application
(thick client) and this will be deployed in all client machines.

We don't want to install SQL server notification services in all client
machines.

We don't to use the ASP.net based subscription management application
also.

Can you recomment any better solution?

Thanks.

Regards,
R.Balaji


"Joe Webb" wrote:



For each client machine, you'll need to run "NSControl register ...".
Doing so will allow you to specify the server. Since these will be
subscriber app clients only, do not specify the -service parameter.

For more information look up "NSControl Register" in BOL.


HTH...
Joe Webb
SQL Server MVP

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



jplankala wrote:


Hi

I have a Notification service created and running  on a remote server.
I

have  a windows application for managing the subscriptions. I want to
have

this windows subscription application installed on different client
machines

for the different users. All the Client machines should acess the same
Notification services and Database. How can I access a Notification
service

running on a remote machine? I do not see any parameters for specifying
the

Servername in the NSInstance constructor.

Please help me to resolve this issue.

Thanks,
Jplankala.





<Prev in Thread] Current Thread [Next in Thread>
  • Re: Accessing Notification Services using a remote client applicat, Joe Webb <=