Posted: 9/5/2013 7:14:07 AM EDT
|
The last time I wrote a remote service or client server application was probably 6 years ago. I did it then in VS2005. I cannot remember how I did it. I have since fell into the automation world and haven't written much direct windows stuff since.
I was reading a bit on WCF. Would this work? It's driving me nuts that I don't have my old source code to reference, but such is life. I need to write a small client server app to check if a set of applications is running on each client machine. The client and application info will be stored in a database. I can write the code to do the checking, but the communications is what I need to figure out. So basically. - server sends list of apps to client(s). - client checks if they are running. - client sends back running or not to the server. So I need to initiate a method or two on the clients and pass a few arrays around. I need to do this with probably 50 or so clients. I would rather have connections opened and closed per session. maybe polling these guys 1/hr or so. Alternatively I could set the clients up to request updated lists from the server and do their own checking periodically. But they need to update the server also. This is to do high level monitoring of unmanned computers. I need to do this without IIS or any other similar web service. |
|
WCF is fucking awesome. Combine that with ADO Entity Framework and now you are cooking. Also, NetTCP binding, fuck IIS. ETA useful WCF links. |
|
Quoted:
No client would be perfect. WMI. I need to research this I guess. Quoted:
Quoted:
Why do you even need a client - can you not poll the servers directly remotely, say with WMI to see if X,Y,Z processes are active or if A,B,C services are running? No client would be perfect. WMI. I need to research this I guess. Grab the toolkit - nice for browsing the classes and testing bits of WQL. WMI Toolkit WQL is the query "language" for WMI, pseudo SQL. ex: Select * From Win32_PerfFormattedData_PerfProc_Process WHERE x=y Win32_PerfFormattedData_PerfProc_Process being one of the many classes exposed by WMI. You can drive this from your processing server from something as simple as a powershell script, perl, VB, C#, or pretty much whatever your are comfortable with. |
|
Quoted:
Grab the toolkit - nice for browsing the classes and testing bits of WQL. WMI Toolkit WQL is the query "language" for WMI, pseudo SQL. ex: Select * From Win32_PerfFormattedData_PerfProc_Process WHERE x=y Win32_PerfFormattedData_PerfProc_Process being one of the many classes exposed by WMI. You can drive this from your processing server from something as simple as a powershell script, perl, VB, C#, or pretty much whatever your are comfortable with. Quoted:
Quoted:
Quoted:
Why do you even need a client - can you not poll the servers directly remotely, say with WMI to see if X,Y,Z processes are active or if A,B,C services are running? No client would be perfect. WMI. I need to research this I guess. Grab the toolkit - nice for browsing the classes and testing bits of WQL. WMI Toolkit WQL is the query "language" for WMI, pseudo SQL. ex: Select * From Win32_PerfFormattedData_PerfProc_Process WHERE x=y Win32_PerfFormattedData_PerfProc_Process being one of the many classes exposed by WMI. You can drive this from your processing server from something as simple as a powershell script, perl, VB, C#, or pretty much whatever your are comfortable with. Perfect. That was a hell of a lot easier than I was going to make it out to be. I owe you a beer. proof of concept complete. Now I just need to spend a few days polishing up an HMI. |
|
Quoted:
Perfect. That was a hell of a lot easier than I was going to make it out to be. I owe you a beer. proof of concept complete. Now I just need to spend a few days polishing up an HMI. Quoted:
Quoted:
Quoted:
Quoted:
Why do you even need a client - can you not poll the servers directly remotely, say with WMI to see if X,Y,Z processes are active or if A,B,C services are running? No client would be perfect. WMI. I need to research this I guess. Grab the toolkit - nice for browsing the classes and testing bits of WQL. WMI Toolkit WQL is the query "language" for WMI, pseudo SQL. ex: Select * From Win32_PerfFormattedData_PerfProc_Process WHERE x=y Win32_PerfFormattedData_PerfProc_Process being one of the many classes exposed by WMI. You can drive this from your processing server from something as simple as a powershell script, perl, VB, C#, or pretty much whatever your are comfortable with. Perfect. That was a hell of a lot easier than I was going to make it out to be. I owe you a beer. proof of concept complete. Now I just need to spend a few days polishing up an HMI. 
|