<br>Hello again,<br><br>Very Happy from your feedback, I will work hard to finish a nice preview version of bbwin.<br><br>For the moment, you can try the bbwincmd.exe (sourceforge : project bbwin ) program which is using the hobbit class protocol I wrote which is actually embeded in the
bbwin.exe service which is then used by every agent via some callback mechanism. This means that a lot of code is already in the bbwin core, so native agents are then very easy to develop and it doesn't need hundreds of redundant code lines. It just need to be written in C++. (not the .det C++ managed ).
<br><br><br><br><div><span class="gmail_quote">2006/3/1, Aiello, Steve (GE, Corporate, consultant) <<a href="mailto:steve.aiello@ge.com">steve.aiello@ge.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><font color="#0000ff" face="Arial" size="2"><span>That
looks great to me, now you have me all excited ;) Awesome that you have put such
effort into this, and I know everyone appreciates it. If there is anything
I can do to assist, happy to help.</span></font></div>
<blockquote style="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div></div>
<div dir="ltr" align="left" lang="en-us"><font face="Tahoma" size="2"><span class="q">-----Original Message-----<br><b>From:</b> Etienne Grignon
[mailto:<a href="mailto:etienne.grignon@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">etienne.grignon@gmail.com</a>] <br></span></font><div><span class="e" id="q_109b66e6348dea2d_2">
<font face="Tahoma" size="2"><b>Sent:</b> Wednesday, March 01, 2006
10:23 AM<br><b>To:</b> <a href="mailto:hobbit@hswn.dk" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">hobbit@hswn.dk</a><br><b>Subject:</b> Re: [hobbit]
Feasibility of Windows Client<br><br></font></span></div></div><div><span class="e" id="q_109b66e6348dea2d_4"><br>Hi Steve,<br><br>Of
course, that was one of the principal objective. Be able to keep the scripts
already developped as externals for quest bbnt.<br><br>You will just need to
change the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Quest
Software\BigBrother\bbnt\ExternalPath to point to the bbwin temporary path and
add the script path to the bbwin externals agents configuration which is in
charge to execute the external, get the results from temporary folder and send
it to the hobbit server. You will be able to develop easily native bbwin
agents dll. As I said, cpu, disk and memory are written as native agents as
the externals agent. It will be very powerful. People will be able to improve
agents or create new one as they were already doing with externals. So, if you
launch bbwin with no loading agent directive, it will do nothing :) <br><br>So
for bbwin, this is the recipe :<br>- agents : native agent dll loaded and
launched in a separate bbwin thread<br>- externals : scripts or executables
launched in their own process. (need the externals.dll agent loaded)
<br><br>Here is the sample bbwin configuration file :<br><br><?xml
version="1.0" encoding="utf-8"
?><br><configuration><br><bbwin><br>
<setting name="hostname" value="myhost" /> <br>
<setting name="bbdisplay" value="myhobbitserver.local:1984"
/><br> <setting name="timer" value="300"
/><br> <load name="externals" value=" externals.dll"
/><br> <load name="uptime" value="uptime.dll"
/><br> <load name="cpu" value="cpu.dll"
/><br> <setting name="debuglevel" value="0" />
<br> <setting name="logpath"
value="C:\BBWin.log"/><br></bbwin><br><externals><br>
<setting name="timer" value="300" /><br> <setting
name="logstimer" value="60" /> <br> <load name="timer"
timer="300" value="timer.vbs" /><br> <load name="wlbs"
value="wlbs.vbs"
/><br></externals><br><cpu><br> <setting
name="alwaysgreen" value="false" /> <br> <setting
name="warnlevel" value="90" /><br> <setting
name="paniclevel" value="95" /><br> <setting
name="delay" value="5" /><br></cpu>
<br><uptime><br></uptime><br></configuration><br><br><br>Tell
me what do you think about it.<br><br>--<br>Etienne<br><br><br>
<div><span class="gmail_quote">2006/3/1, Aiello, Steve (GE, Corporate,
consultant) < <a href="mailto:steve.aiello@ge.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">steve.aiello@ge.com</a>>:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><span><font color="#0000ff" face="Arial" size="2">With your BBWin, will there
be the abbility to run customs external scripts ? Alot of my existing
scripts are written in VBS.</font></span></div>
<blockquote style="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div></div>
<div dir="ltr" align="left" lang="en-us"><font face="Tahoma" size="2"><span>-----Original Message-----<br><b>From:</b> Etienne Grignon
[mailto:<a href="mailto:etienne.grignon@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">etienne.grignon@gmail.com</a>] <br></span><span><b>Sent:</b> Wednesday, March 01, 2006 9:24 AM
<br><b>To:</b> <a href="mailto:hobbit@hswn.dk" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">hobbit@hswn.dk</a><br></span><span><b>Subject:</b>
Re: [hobbit] Feasibility of Windows
Client<br><br></span></font></div><span>Hi Steve, Hi
Peter,<br><br><br>Well, with BBWin, you will be able to compile it without
cygwin because I use all win32 possibilities :) And the source code of
BBWin is under GPL, so no more problem :) <br><br>About the hobbit
protocol, the agent will be able to use data messages so, I some agents
will be able to send status message used for the web page, and data
message in an easier format to be able to parse it on hobbit server side.
For the moment, I'm trying to get the same format than the original quest
bbnt client to be able to use the existing rrd parsing scripts. Of course,
in the future, we can imagine to report status and data in a similar
format than the today hobbit unix client. <br><br><br>About WMI, I will
only use if I can't do it using native C++ api. For example, I have made a
nice external vbs using WMI to monitor my windows wlbs (NLB) clusters
because no C api was available. However, for the MSCS clusters, even if
it's possible to make it with WMI, I had prefered make the external with
the native C api. So, note that you will be soon be able to monitor easily
the two sorts of Microsoft clusters :) These 2 probes will be integrated
in the preview release. (If I have enough time, MSCS external will be
released as a native bbwin agent :) ) <br><br>After posting the preview
release, I think I will be able to implement a new probe each 2 weeks, so
I will try to work as Henrik :<br><br>1) first post the idea with my
implementation idea<br>2) recolt all your ideas and remarks <br>3) merge
the all and implement it <br><br><br>If anyone has ideas about the
project, don't hesitate to post or to send me directly an email
:)<br><br><br>Peter : I did't get the attached file you posted, it doesn't
seem to be present
<br><br>--<br>Etienne<br><br></span></blockquote></blockquote></div><br><br clear="all"><br>-- <br>Etienne GRIGNON </span></div></blockquote>
</blockquote></div><br><br clear="all"><br>-- <br>Etienne GRIGNON