3. Does WebNMS Multi-Protocol agent
deal with restricting/limiting access to MBeans based on an
The WebNMS Multi-Protocol agent has implemented the View-Based
Authorization Service that will help you restrict/ limit access
to MBeans based on user authentication.
The user authentication is not common across all the adaptors
but depends on the adaptor implementation. Each user is configured
a particular view and this view determines the access for
that user. Also, this service in itself is implemented as
a managed object, so that the configurations can remotely
be managed without restarting the agent. This gives the flexibility
to add, delete, and modify users and their configuration at
5. Does WebNMS offer any service to
discover multi-protocol agent in the network? If so, how are
the agents discovered only on the localhost?
Yes. WebNMS offers discovery service that discovers multi-protocol
agent in the network. This service relies on a discovery client
object, which sends out multi-cast requests to find agents.
Refer to "Discovery
Service" section of the help documentation, to know
more about implementing the service.
6. When WebNMS Multi-Protocol agent
crashes, does the restart of the agent require to restart
all the other applications that were being managed earlier
This is not mandatory, if the application is running on a
different JVM. Once the JMX server restarts, it has to connect
to the applications managed and get the management interface
( MBeans) for the applications.