|
|
Protocol adaptors provide a view of the agent and its registered MBeans through a basic interface on the protocol-specific browser. The adaptor could be plugged into the MBean Server as an MBean to render manageability to it. This offers greater flexibility to its operation as it can be invoked or stopped from service through any of the other available adaptors.
To plug in an adaptor, do the following steps:
Name the MBean with a meaningful object name.
Instantiate the class with a constructor allowing the user to specify a non-default port.
Register the MBean with the MBean server.
Start the adaptor to make it active.
All the adaptors must extend the abstract class Abstract Adaptor, which captures the common behavior of all the adaptors. This implements the following interfaces: Adaptor, MBeanRegistration, NotificationBroadcaster, and Serializable. The AbstractAdaptor class contains many methods, which define some of the generic behavior exhibited by all the adaptors.
Functions of some of these methods are listed below:
Returns the host on which the adaptor resides
Returns the port at which the adaptor listens
Returns the state of the adaptor
Returns the state of the adaptor in string format
Sets the port at which the adaptor is listening
Starts the Adaptor
Stops the Adaptor
Adds Notification Listener
Removes Notification Listener
Implementation of custom protocol adaptors and the methods available for the same are explained in the chapter 5.19 "Writing custom protocol adaptors for the Multi-Protocol agent "
9.2 Protocol Adaptors Supported by the Multi-Protocol agent
The advantage with Multi-Protocol agent is that it provides access to a common code through multiple protocols. The generated code is common and needs to be instrumented only once. This instrumentation is made available through all the adaptors/protocols. The AdventNet Multi-Protocol agent supports the following protocol adaptors.
|
|