A web service interface would be how I'd do it. This really decouples server from the client and allows you the ability to use many different types of applications on the client-side to communicate with the server. Utilizing WMI within the services would also be part of going this route. WMI is a bit confusing at first, but offers the greatest amount of flexibility. There are also several libraries that can be used to abstract your code from the nitty-gritty of WMI and see it as a control layer.
manpreet
Best Answer
2 years ago
I contribute to a cluster of C++ and C# servers that publish data statistics, connection status, and management commands for use by a management client. The current implementation uses custom middleware.
Code for both the servers and the client can be changed. I am considering migration to some standard management solution to simplify the code and improve stability. The potential to use 3rd party tools would also be a plus.
What technology should I use for the management interface ... WMI? It seems to be the default, but I don't see a lot of current books or articles. Or should I expose some common web service? Or?