All Packages from org.jboss.jmx.adaptor.* to org.jboss.jmx.service.*

Home >> All >> org >> jboss >> jmx

•

Package Samples:

• org.jboss.jmx.adaptor.ejb
• org.jboss.jmx.adaptor.rmi
• org.jboss.jmx.adaptor.xml
• org.jboss.jmx.connector
• org.jboss.jmx.connector.ejb
• org.jboss.jmx.connector.notification
• org.jboss.jmx.connector.rmi
• org.jboss.jmx.service
• org.jboss.jmx.adaptor.control
• org.jboss.jmx.adaptor.html
• org.jboss.jmx.adaptor.model
• org.jboss.jmx.connector.invoker.client
• org.jboss.jmx.connector.invoker
• org.jboss.jmx.adaptor.snmp.agent
• org.jboss.jmx.adaptor.snmp.test
• org.jboss.jmx.adaptor.snmp.trapd

Classes:

• TrapFactorySupport: TrapFactorySupport takes care of translation of Notifications into SNMP V1 and V2 traps Data Structure Guide It looks complicated but it ain't. The mappings are read into a structure that follows the outline defined in the Notification.xsd. Have a look there and in the example notificationMap.xml and you should get the picture. As an optimization, 2 things are done: 1. The "NotificationType" fields of all the mappings are read, interpreted and compiled as regular expressions. All the instances are placed in an array and made accessible in their compiled form 2. The "wrapperClass" attribute is interpreted ...
• NotificationWrapper: NotificationWrapper is a "wide" read only interface providing "unstructured" access to agent internals and paylod carried by notifications. The alternatives were: 1. Precompile assumptions regarding the notification stucture and its payload in the trap factory 2. Use introspection but with a potential large execution overhead. The use of delegated wrappers stands somewhere in the middle. Trap factory can be extended with the definition and use of new wpappers that will be able to cope with any kind of notfications. Run time overhead is minimal as wrappers can be instantiated only once. Tags used ...
• TrapFactory: TrapFactory takes care of translation of Notifications into SNMP V1 and V2 traps Trap-PDU ::= [4] IMPLICIT SEQUENCE { enterprise -- type of object generating -- trap, see sysObjectID in [5] OBJECT IDENTIFIER, agent-addr -- address of object generating NetworkAddress, -- trap generic-trap -- generic trap type INTEGER { coldStart(0), warmStart(1), linkDown(2), linkUp(3), authenticationFailure(4), egpNeighborLoss(5), enterpriseSpecific(6) }, specific-trap -- specific code, present even INTEGER, -- if generic-trap is not -- enterpriseSpecific time-stamp -- time elapsed between the last TimeTicks, -- ...
• TestClient: Test Client for the JMX Client Connector. It cretes a local MBeanServer and adds the ConnectorFactory as first MBean. Then it will use the ConnectorFactory to local servers on the net and then to locate its offered protocols (Server side Connectors). After the user selected and server and a protocol its client-side connector will be loaded through the ConnectorFactory and a connection to the server will be established. Now the offered MBean on the remote server and its attributes and operations will be listed and at the end this test client will add a notification listener to all MBeans on the ...
• EJBConnector: This is the equivalent to the RMI Connector but uses the EJB Adaptor. The only advantage of using EJB-Adaptor is that you can utilize the security. ATTENTION : Note that for the event transport (or in the JMX Notations: Notification) the server must be able to load the RMI Stubs and the Remote Listener classes. Therefore you must make them available to the JMX Server and the EJB-Adaptor (meaning the EJB-Container). Translates RemoteExceptions into MBeanExceptions where declared and RuntimeMBeanExceptions when not declared. RuntimeMBeanException contain NestedRuntimeException containg the root RemoteException ...
• InvokerAdaptorService: A JBoss service exposes an invoke(Invocation) operation that maps calls to the ExposedInterface onto the MBeanServer this service is registered with. It is used in conjunction with a proxy factory to expose the MBeanServer to remote clients through arbitrary protocols. It sets up the correct classloader before unmarshalling the arguments, this relies on the ObjectName being seperate from from the other method arguments to avoid unmarshalling them before the classloader is determined from the ObjectName. The interface is configurable, it must be similar to MBeanServer, though not necessarily derived ...
• RegExpNotificationFilterSupport: RegExpNotificationFilterSupport is responsible for checking the matching of notifications against constraints defined by the notification listener. The constraints are defined as regular expressions and the filtering is performed on the notification type attribute. The notification type is sequentially checked against the contained regular expressions until a match is found or all the expressions have been checked.
• SnmpVarBindFactory: SnmpVarBindFactory implements the infrastructure required to generate SNMP variable bindings from generic Object instances. For each handled type (integer, string, e.t.c.) a corresponding maker class is present that "knows" how to make and populate the coresponding variable binding (SnmpInt32, SnmpOctetString). The mapping between types and makers is held in a hash map for optimised performance.
• DynamicContentAccessor: DynamicContentAccessor or DCA for short allows the introduction of dynamic content in the notification wrappers. The later contain static values keyed on a tag. The problem solved from DCA instances regards the access of volatile content. In other words when a DCA implementation is accessed, its get method will provide access to whatever content it is designed to.
• TestServer: Test Program for the JMX Connector over RMI for the server-side. It creates a local MBeanServer, loads the RMI Connector and registered it as a MBean. At the end it will bind it to the local JNDI server (us your own or download the ??.jar and ??.properties from jBoss). Afterwards you can download connector.jar from jBoss and test the connection.
• SnmpAgentService: SnmpAgentService is an MBean class implementing an SNMP agent. Currently, it allows to send V1 or V2 traps to one or more SNMP managers defined by their IP address, listening port number and expected SNMP version. It will hopefully grow into a full blown SNMP agent with get/set functionality.
• RMINotificationListener: Notification Listener Implementation registered as MBean on the remote JMX Server and the added as Notification Listener on the remote JMX Server. Each notification received will be transfered to the remote client using RMI Callback Objects.
• TrapdService: MBean wrapper class that acts as an SNMP trap receiver/logger. It logs traps as INFO messages - change log4j configuration to redirect logging output. To reconfigure the listening port the MBean needs to be stopped and re-started.
• TrapEmitter: TrapEmitter is a class that manages SNMP trap emission. Currently, it allows to send V1 or V2 traps to one or more subscribed SNMP managers defined by their IP address, listening port number and expected SNMP version.
• NotificationProducerService: NotificationProducerService is a test class with an MBean interface used to produce simple JMX notifications to be intercepted and mapped to SNMP traps by the snmp JMX adaptor
• ConnectorFactoryImpl: Factory delivering a list of servers and its available protocol connectors and after selected to initiate the connection This is just the (incomplete) interface of it
• RMIClientNotificationListener: Client-side RMI Listener to receive the message and send to the clients listener. Its stub is used on the server-side to hand the Notifications over to this class.
• Clock: Utility class that provides time keeping from the time of instantiation. Can be queried for time readings since the last incarnation in msecs.
• RMIRemoteMBeanProxy: A factory for producing MBean proxies that run on a distant node and access the server through RMI. Most of the code comes from MBeanProxy.
• Counter: Simple, thread safe counter implementattion with accessor methods. (Maybe replace with EDU.oswego.cs.dl.util.concurrent.SynchronizedLong?)
• RMIAdaptor: RMI Interface for the server side Connector which is nearly the same as the MBeanServer Interface but has an additional RemoteException.
• RMIAdaptorImpl: RMI Interface for the server side Connector which is nearly the same as the MBeanServer Interface but has an additional RemoteException.
• SubscriptionMgr: SubscriptionMgr is responsible for subscribing a notification listener to all objects defined in the coresponding resource file.
• MappingFailedException: MappingFailedException is used to report generic errors encountered during the translation from notifications to traps.

Home | Contact Us | Privacy Policy | Terms of Service