Tell me something... do you propagate events in the connector?
if not they would need to be JMS messages.
|Can you specify this a little bit more to which MBeans you want offer EJB
|interfaces
|and what you want to be done remotely?
sure, essentially every service that is in j2ee (a container, a web
container, a jms service, a pool service, a naming service etc etc) exposes
some management functionality
1- the basic start/stop operations
2- state set/get on these services
that's it it is the heart of JSR77
we would propose a naming and interface to talk to them remotely through
java tools (as opposed to SNMP consoles). As I said 1and 2 the industry is
ok on the bare definitions. For the java access to them we are pioneering,
I believe that for the price of copying the MIB in EJB (where the home is
the "JDBCPOOLHome" and then we can create a bean or findByPK to a given pool
and Object is the mib equivalent) then we can remotely administer "for free"
the server.
Events are another ballgame but essentially we would expose the queues in
JNDI just the same
marc
|
|Thanx Andy
|
|
|
|
