Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

org.opennms.ant.* (1)org.opennms.core.* (27)org.opennms.netmgt.* (276)
org.opennms.protocols.* (56)org.opennms.report.* (13)org.opennms.test.* (11)
org.opennms.web.* (206)

Package Samples:

org.opennms.ant
org.opennms.web.element
org.opennms.web.admin.pollerConfig
org.opennms.web.admin.users.parsers
org.opennms.web.admin.users
org.opennms.web.admin.views.parsers
org.opennms.web.admin.views
org.opennms.web.admin.groups.parsers
org.opennms.web.admin.groups
org.opennms.web.admin.nodeManagement
org.opennms.web.admin.notification.noticeWizard
org.opennms.web.admin.notification
org.opennms.web.admin.config
org.opennms.web.availability.raw
org.opennms.web.availability
org.opennms.web.event.filter
org.opennms.web.event
org.opennms.web.notification.bobject
org.opennms.web.notification.parsers
org.opennms.web.notification

Classes:

HttpPlugin: This class is designed to be used by the capabilities daemon to test for the existance of an HTTP server on remote interfaces. The class implements the CapsdPlugin interface that allows it to be used along with other plugins by the daemon. This plugin generates a HTTP GET request and checks the return code returned by the remote host to determine if it supports the protocol. The remote host's response will be deemed valid if the return code falls in the 100 to 599 range (inclusive). This is based on the following information from RFC 1945 (HTTP 1.0) HTTP 1.0 GET return codes: 1xx: Informational ...
OutageWriter: When a 'nodeLostService' is received, it is made sure that there is no 'open' outage record in the 'outages' table for this nodeid/ipaddr/serviceid - i.e that there is not already a record for this n/i/s where the 'lostService' time is known and the 'regainedService' time is NULL - if there is, the current 'lostService' event is ignored else a new outage is created The 'interfaceDown' is similar to the 'nodeLostService' except that it acts relevant to a nodeid/ipaddr combination and a 'nodeDown' acts on a nodeid When a 'nodeRegainedService' is received and there is an 'open' outage for the nodeid/ipaddr/serviceid, ...
EventsArchiver: The EventsArchiver is responsible for archiving and removing events from the 'events' table. The archival/deletion depends on the 'eventLog' and the 'eventDisplay' values for the event - If the 'eventLog == N and the eventDisplay == N', the event is simply deleted from the events table If the 'eventLog == N and the eventDisplay == Y', the event is deleted ONLY if the event has been acknowledged If the 'eventLog == Y and the eventDisplay == N', the event is sent to the archive file and deleted from the table If the 'eventLog == Y and the eventDisplay == Y', the event is sent to the archive file ...
EventExpander: This class is responsible for looking up the matching evenconf entry for an event and loading info from the eventconf match to the event. This class is also responsible for the event parm expansion Notes on event parm expansion: The list of elements that can have a %element% or %parms[*]% in their value are : descr, logmsg, operinstr, autoaction, operaction(/menu), tticket The list of elements that can occur as a %element% are : uei, source, nodeid, time, host, interface, snmphost, service, snmp, id, idtext, version, specific, generic, community, severity, operinstr, mouseovertext, parm[values-all], ...
Dhcpd: The DHCP client daemon serves as a multiplexor for DHCP requests and responses. The Bootp/DHCP protocol specifies that a DHCP server listens for requests on local UDP/67 and will either send/broadcast responses to UDP/68 or will unicast responses back to the client's UDP port on from which the request originated. The DHCP daemon accepts client connections on TCP/5818. Once a client is connected it can begin forwarding requests. A list of all currently connected clients is maintained. Requests have the following format: byte 1 - byte 4 : 32-bit remote host IP address byte 5 - byte 8 : 32-bit buffer ...
snmpwalk: This class is designed to provide an example of how to use the JoeSNMP libraries from OpenNMS . This example illustrates the code required to walk an SNMP tree of an individual agent on a remote host. The class will walk the entire agent tree, or a subsection, as defined by the command line arguments. Through the command line options it is possible to set the community string, timeouts, retries, and other options used by the JoeSNMP library. Usage: java org.opennms.test.snmpwalk [options] remote-host [object-id] The command line options are as follows: -v 1 || 2 || 2c Sets the SNMP protocol version. ...
snmpwalkmv: This class is designed to provide an example of how to use the JoeSNMP libraries from OpenNMS . This example illustrates the code required to walk an SNMP tree of an individual agent on a remote host. The class will walk the entire agent tree, or a subsection, as defined by the command line arguments. Through the command line options it is possible to set the community string, timeouts, retries, and other options used by the JoeSNMP library. Usage: java org.opennms.test.snmpwalk [options] remote-host [object-id] The command line options are as follows: -v 1 || 2 || 2c Sets the SNMP protocol version. ...
RRDInfo: A data structure encapsulating information about a single round robin database (RRD). This class holds all the data from the rrdtool info command in a single, object-oriented data structure/JavaBean. To create an instance of this object, call the static createRRDInfo 55 method with the output from an rrdtool info command. This data usually looks something like: filename = "129.1.1.208-localhost.rrd" rrd_version = "0001" step = 300 last_update = 982079322 ds[EXPANSION_COUNTER_1].type = "COUNTER" ds[EXPANSION_COUNTER_1].minimal_heartbeat = 600 ds[EXPANSION_COUNTER_1].min = NaN ds[EXPANSION_COUNTER_1].max ...
HttpsPlugin: This class is designed to be used by the capabilities daemon to test for the existance of an HTTPS server on remote interfaces. The class implements the CapsdPlugin interface that allows it to be used along with other plugins by the daemon. This plugin generates a HTTP GET request and checks the return code returned by the remote host to determine if it supports the protocol. The remote host's response will be deemed valid if the return code falls in the 100 to 599 range (inclusive). This is based on the following information from RFC 1945 (HTTP 1.0) HTTP 1.0 GET return codes: 1xx: Informational ...
Fiber: The Fiber interface is similar to the core Java language Thread class. The Fiber class is used to define a working context , which is the basic feature of a Thread . The differences end there since the Thread class is part of the core language and can only be extended since it is a concrete class. The Fiber concept is used to represent an implementation defined execution context outside of the core Java language. It provides a very loose definition of what and how a Fiber should behave. This gives a great deal of implementation independence to the implementing classes. For example, the Fiber interface ...
ThresholderUpdates: The ThresholderUpdates class encapsulates changes to a SnmpThresholder which is actively being threshold checked by the threshd scheduler. When associated with a SnmpThresholder object the updates represented by the class are to be applied to the SnmpThresholder AFTER being popped from the interval queues for scheduling but BEFORE the next collection takes place. This is necessary because it isn't possible to make modifications to the SnmpThresholder objects at the time that a particular event is received by the BroadcastEventProcessor class...the interface may in fact be in the process of being ...
CollectorUpdates: The CollectorUpdates class encapsulates changes to a SnmpCollector which is actively being collected by the collectd scheduler. When associated with a SnmpCollector object the updates represented by the class are to be applied to the SnmpCollector AFTER being popped from the interval queues for scheduling but BEFORE the next collection takes place. This is necessary because it isn't possible to make modifications to the SnmpCollector objects at the time that a particular event is received by the BroadcastEventProcessor class...the interface may in fact be in the process of being collected. So we ...
PollableServiceProxy: A proxy to a PollableService which acts as a surrogate for rescheduling purposes. This was created as a temporary fix to allow us to schedule a PollableService for a sooner execution, despite the fact that it is already scheduled for a later time. At the time we created this class, the Scheduler did not provide any means to cancel or reschedule an element on its queue. Therefore, this workaround became necessary. In order to use this class, create an instance of it with the desired PollableService and the timestamp at which you want it to run. Once you have the instance, you can schedule it with ...
ReplyReceiver: This class is designed to be a single point of reciept for all ICMP messages received by an IcmpSocket instance. The class implements the PausableFiber interface as a means to control the operation of the receiver. Once the receiver is started it will process all recieved datagrams and filter them based upon their ICMP code and the filter identifier used to construct the reciever. All ICMP messages, except for Echo Replies, are discared by the reciever. In addition, only those echo replies that have their identifier set to the passed filter identifier are also discarded. Received datagrams that ...
ServiceMonitor: This is the interface that must be implemented by each poller plugin in the framework. This well defined interface allows the framework to treat each plugin identically. When a service monitor plug-in is loaded and initialized, the framework will initialize the monitor by calling the initialize() method. Likewise, when the monitor is unloaded the framework calls the release() method is called. If the plug-in needs to save or read any configuration information after the initialize() call, a reference to the proxy object should be saved at initialization. NOTE: The plug-in poll() must be thread safe ...
RTCManager: The RTCManager maintains data required so as to calculate availability for the different categories configured in categories.xml The RTC initializes its data from the database when it comes up. It then subscribes to the Events subsystem to receive events of interest to keep the data up-to-date Availability data is sent out to listeners who indicate that they are listening by sending an RTC 'subscribe' event. The subscribe event has an URL and user/passwd info. so RTC can post data to the URL The RTC has two timers(a low threshold and a high threshold) and a counter that can run upto a configurable ...
Manager: The Manager is reponsible for launching/starting all services in the VM that it is started for. The Manager operates in two modes, normal and server normal mode: In the normal mode, the Manager starts all services configured for its VM in the service-configuration.xml and starts listening for control events on the 'control-broadcast' JMS topic for stop control messages for itself server mode: In the server mode, the Manager starts up and listens on the 'control-broadcast' JMS topic for 'start' control messages for services in its VM and a stop control messge for itself. When a start for a service ...
DNSAddressRequest: The DNSAddressRequest holds a DNS request to lookup the IP address of a host - provides for transmitting and receiving the response for this lookup. NOTES: A DNS request and response has the following fileds header questions answers authorities additional information The header has the following format: id - unique id sent by the client and returned by the server in its response 16 bits of flags - Query(0)/response(1) flag opcode - that has type of query AA - set if the response is an authoritative answer TC - set if response is truncated RD - set if recursion is desired RA - set if recursion is ...
Eventd: Eventd listens for events from the discovery, capsd, trapd processes and sends events to the Master Station when queried for. Eventd receives events sent in as XML, looks up the event.conf and adds information to these events and stores them to the db. It also reconverts them back to XML to be sent to other processes like 'actiond' Process like trapd, capsd etc. that are local to the distributed poller send events to the eventd. Events can also be sent via TCP or UDP to eventd. Eventd listens for incoming events, loads info from the 'event.conf', adds events to the database and sends the events ...
DbNodeEntry: This class is used to model a row of the node table from the OpenNMS database. The node table is indexed by the elements dpNode and nodeID . When a new element is created using the create call a node id will be automatically defined. If the name of the distribute poller is not passed to the create method, the it also is assigned a default value. Once loaded or create, the class tracks any changes and will write those changes to the database whenever the store method is invoked. If a database conneciton is not passed to the store method, then a temporary one is allocated to write the results. NOTE: ...
SimpleDbConnectionFactory: A trivial implementation of DbConnectionFactory that creates a new connection for every request and does no caching or connection sharing. Note that no real connection pooling is occurring within this class. This factory will be an inefficient connection management scheme for most real-world applications. It was designed only for development/debugging purposes and for applications that are very infrequently used. In those cases, caching idle database connections for long periods of time can be wasteful, and this pooling scheme would be appropriate. This manager simply initializes the JDBC driver ...
RRDGraphServlet: A servlet that creates a graph of network performance data using the RRDTool . This servlet executes an rrdtool graph command in another process, piping its PNG file to standard out. The servlet then reads that PNG file and returns it on the ServletOutputStream . This servlet requires the following parameters: report The name of the key in the rrdtool-graph properties file that contains information (including the command line options) to execute specific graph query. rrd The name of the ".rrd" file to graph. The file must exist in the input directory specified in the rrdtool-graph properties file. ...
IfXTableEntry: This object contains a list of all the elements defined in the MIB-II interface extensions table. An instance object is initialized by calling the constructor and passing in a variable list from an SNMP PDU. The actual data can be recovered via the base class map interface. Once an instance is created and its data set either via the constructor or from the update method, the actual elements can be retreived using the instance names. The names include: ifName , ifInMulticastPts , ifInBroadcastPkts , etc al . The information can also be accessed by using the complete object identifer for the entry. ...
BBParser: BBParser provides basic XML parsing functionality to parse XML from a file or an input stream BBParser creates a DOMParser which creates a DOM tree of the XML being parsed. BBParser provides the error handling routines for the DOM parser and provides some methods to traverse the elements of the DOM tree created as a result of the parse. The DOMParser created throws an IOException if the xml file is not found or if the xml does not conform to its DTD. In addition to this, BBParser and its sub-classes can set their own exception messages and throw exceptions if the values read are not what is expected. ...
IPv4NetworkInterface: The NetworkInterface class is designed to be a well defined front for passing interfaces to a service monitor. There are many different types of network in use today including IPv4, IPv6, IPX, and others. To accomidate the possible differences this class provides the basic information that a monitor can use to determine the type of interface and its expected address type. In addition to providing typing and address information, the interface allows for the monitor to associate key-value pairs with an interface. This can be used to save state information between the various invocations if neccessary. ...

Home | Contact Us | Privacy Policy | Terms of Service