The CentralStatus sample is an ASP .NET project that uses SOAP to communicate with a number of ipMonitor instances and display status information on a single web page.
With this sample, you can:
ipMonitor SOAP Methods Used (C#):
Our goal for this project is to showcase how to retrieve real-time status information in ASP .NET with as little "display formatting" as possible. Our technique is to collect status information and store it in the following tree format:
Class View, Courtesy of Microsoft Visual Studio .NET 2003
SOAP Sample Breakdown, by File:
The C# project that contains everything needed to compile the web application. Note: you will likely have to change the webinfo file to correspond to the location of centralstatus.csproj.
Settings for the sample; includes refresh rates, password and account info, and location of servers. This file is intentionally left out of the wwwroot so it doesn't get downloaded. (Later we'll expand this sample to show the usage of "utility.LoadWithMachineKey" so passwords and accounts aren't stored out in the open.)
ASP .NET compiled code to run behind the aspx pages.
Applicaton "global" object (receives application events) and is where we create our ipm7ServerList and start the thread that keeps it up-to-date. Note that the centralstatus.xml is read in the global.aspx.cs file.
Display formatting css data for use with centralstatus.aspx.
A couple of our utility functions to make the sample function. Note: RewindPath is how we locate the centralstatus.xml.
.\wwwroot\ipm_cookies.js & .\wwwroot\ipm_serialize.js
Images used for display within centralstatus.aspx
The after effects of consuming the ipMonitor Status WSDL
For information on other features and concepts related to those discussed in this article, refer to the following ipMonitor resources:
Last Updated: March 30, 2004 | What did you think of this topic?