>> The persistency database is constantly kept up to date.

That’s the way to go, at least for OMNIEvents and at least for monitoring. I’ll have a look.

>> If you need help, then I’m available for contract work.

CORBA projects today are rather rare. Anyway if something moves somewhere, I’ll keep Your name handy.

>> If you want to do it yourself, then I’ll be happy to >> accept patches.

I’ll be glad to contribute. Time permitting, (just like always)…

Ciao,

R

Is there a way to monitor the status of OmniEvents from the outside?

I started on something like that, with a CORBA interface, using the CosPropertyService. Paul Nader continued to work on it, with the goal of producing and SMPT interface that would have provided exactly the sort of functionality you describe. Check out the ‘branch_SNMP’ branch in CVS, to see that work

You might want to contact Paul, and ask him about the work he was doing. His e-mail is on Sourceforge.

Personally, I’m a bit dubious about the benefits of instrumenting the application itself. The persistency database is constantly kept up to date. It contains all the information you want in an easily parsed text form. Why not just read that?

Has someone already written that? (i hate rediscover the wheel)

Great. You’re right - don’t reinvent the wheel.

If you need help, then I’m available for contract work. If you want to do it yourself, then I’ll be happy to accept patches.

-Alex

First of all, thanks for the nice work You’re doing on OmniEvents.

Now, a question:

Is there a way to monitor the status of OmniEvents from the outside? I’m considering writing some kind of ESB based on a open source COSEvents service, and i wonder if someone has already dome something (via interceptors maybe) with OmniEvent.

I’d like to define some kind of tree-based console ginving info on channels and events and allowing some admin operations on them.

Has someone already written that? (i hate rediscover the wheel)

Ciao,

R