Re: A light weight remot application manageability

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

"Bogdan" <nobody@xxxxxxxxxx> wrote in message
news:O2Hul30KGHA.1088@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

I'm developing an mfc app that will run 24x7 and will be installed
potentially in hundreds of remote locations. I need to come up with a way
for the app to report its status back to a management app (yet to be
written). I was thinking of developing the management app as a Web app in
C#/.NET. The basic idea would be for the remote app (or its selected
threads) to 'ping' the Web server (via POST, Web service, etc.) and send
error and special event descriptions on a regular basis. Our IT guys
would
connect to a Web page to view status of the remote apps. The remote apps
will most likely have dynamic IP addresses assigned to them by local
DHCPs.
The Web app could track this info so IT guys can connect to any of the
remote machine if necessary using a third party software (or take other
actions if no feedback from a given machine for a certain duration).

The whole concept sounds a bit like WMI/WBEM. Still, I think that WMI
might be an overkill in this case.

Can someone please point me in a right direction?

If the "remove locations" are scattered, and only accessible via the
internet, then your method sounds reasonable.
I had a similar situation, and had the remove application do a GET (ping w/
some data) to an external website. The external website was a *very* simple
PHP/MySQL website that logged every GET that came in. Then, there was
another application that the IT guys used that would constantly download the
ping-data from the external website, and update an internal-use database.
It worked pretty well, and limited exposure to the ping-data, since its
lifetime on the external server was very short. It also used a nice ISP
with high bandwidth for multiple remove applications to connect
simultaneously and quickly, while the internal IT guys could use our slow
DSL line to gather the information from the external site.

Good luck
DanB


.

Relevant Pages

  • RE: dll problem on Remoting app
    ... Microsoft Online Support ... dll problem on Remoting app ... |> | first time we call a remote method of the remote object(through ...
    (microsoft.public.dotnet.framework)
  • Re: 1st hosting of objects, new(), etc.
    ... > makes sense that New would attempt to create a remote object. ... > application once you have registered a wellknown type in that app domain ... > Register MyObject as a wellknown type ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Advice needed on developing app for linux
    ... >> variety of apps, so why would I need your app to run them within it? ... what you can not see on the screenshot is that everything is remote. ... machine running your component setup control software why would you need ... installed localy when all they actualy need is access to the electronics ...
    (comp.os.linux.development.apps)
  • RE: dll problem on Remoting app
    ... When we register a PB.dll version 1.1 and uses this in our app it fails. ... > | object, the remote object is not actually created or referenced, in other ... The communiation to the remoting server won't happen until ...
    (microsoft.public.dotnet.framework)
  • Re: Run VB6 .exe on server from a remote machine on same network; db is SQL Server 2000
    ... By "runtimes", do you mean the dlls, etc., that the app needs in order to ... > Dave O. ... do you mean that we do not have to also install all the ... >>> Do you mean to run a program from a remote server on a local PC, ...
    (microsoft.public.vb.general.discussion)