Hi Jeff (, Shawn, Frans, Eric...and the other posters in the thread), > I think that Eric below and Chris Hampson are closest with > Enterprise Instrumentation Framework and WMI. It is worth > noting that WMI is a far more general framework than a .NET > equivalent of JMX. System.Diagnostics also has some relevant > parallels to the javax.management.monitor package. > > hope that helps, > Jef > http://integralpath.blogs.com >
Thanks for the suggestions, It seems JMX has no direct .NET counterpart as such. WMI is lower-level and vastly more complex but it seems to have the most overlap feature-wise. I haven't dug in to EIF much (and I'm avoiding unmanaged code options) but, I'm inclined to simply keep using our homegrown JMX-alike stuff. Perhaps also look into adding WMI adaptors. This article introduces some options: http://msdn.microsoft.com/msdnmag/issues/04/04/InstrumentationinNET/default. aspx Kunle > On 6/6/06, Eric Means wrote: > > > > Windows Management Instrumentation (WMI)? > > > > On 6/6/06, Chris Hampson (AU) wrote: > > > > > > Enterprise Instrumentation Framework ? > > > > > > Maybe the BAM component of BizTalk? > > > > > > On 6/6/06, Frans Bouma wrote: > > > > > > > > > > What does JMX do? > > > > > > > > > > It's a spec for application instrumentation, managemenent and > > > > > monitoring. It's "lightweight" enough to be included > in the core > > > > > of some applications (e.g. famously in the JBoss runtime > > > > > kernel). > > > > > > > > .NET doesn't have these kind of standards. In the .NET > > > > world, standards for these kind of things are defined > by products. > > > > Looking at the marketing goo over at Sun, I think it does > > > > something similar as Biztalk wants to do, though Biztalk is > > > > broarder than this and of course far from free. > > > > > > > > FB =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
