jsnmp:http://www.jsnmp.com
jSNMP Enterprise™ provides application developers a cross-platform means of communicating with SNMP devices and services. It is written entirely in Java and is completely portable. jSNMP™ provides complete SNMP v1/v2c/v3 support including trap/inform handling and authentication and privacy password alteration (see RFC 3414).
A traditional Java SNMP SDK, Java SNMP API, or SNMP Java library requires the user to manually construct SNMP request packets. The jSNMP™ interface, however, allows the user to communicate with network devices by specifying the Object Identifier (OID) of interest rather than worrying about the intricacies of SNMP, such as the Basic Encoding Rules (BER) or Protocol Data Unit (PDU) format.
jSNMP™ has been optimized for minimizing network traffic and maximizing efficiency, allowing for a high degree of scalability. In addition, the package has been optimized for use with multiple simultaneous connections, allowing for a 3-tier model.
To support a 3-tier model, jSNMP™ includes the tools necessary to create distributed network management applications using RMI and CORBA. The core jSNMP™ engine can be run as an RMI server. Client applications can be written to use either the RMI interface or a remote version of the easy-to-use jSNMP™ interface. Either way, lightweight clients, running in or out of browsers, can be created using a single back-end jSNMP™ service.
Running jSNMP™ as an RMI server provides a number of distinct benefits. All communication with managed devices flows through the service. This reduces the load placed on the devices, and allows the service to perform several optimizations. For instance, requests bound for the same managed device can be packaged together in one PDU, even if the requests came from different clients. Also, values are cached for a user-defined period of time. If a request is received within the defined time window, a cached value is returned. This removes the need for additional network traffic. Better security, easier administration, and improved trap handling are also possible in a 3-tier model.
The use of a robust RMI server, distributed capabilities, and high-level SNMP Java interfaces, combine to create a powerful combination that will save SNMP developers both time and money.
Since SNMP OIDs are difficult to remember, developers may prefer to make a SNMP request with the name associated with an OID instead of the OID's dotted decimal notation (e.g., ifAdminStatus.1 instead of 1.3.6.1.2.1.2.2.1.7.1). jSNMP Enterprise™ includes the powerful Java MIB compiler jMIBC™, which takes a series of MIB files and produces a dictionary that is used by the jSNMP Enterprise™ SnmpMIBService and SnmpMIBDictionary classes to translate OIDs to/from common names, to retrieve an OID’s status, access, type, abstract type, and description, and to translate OID enumerated values.
