![]() |
|||
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
| ||
1.6.1 Class Containing the SNMP View of a Table (Metadata Class)The metadata class containing the SNMP view of a table contains all the management of the table index. Usually you do not need to subclass or access the generated table Metadata classes, except when implementing virtual tables. See SNMP Virtual Table example in the Java Dynamic Management Kit 5.1 Tutorial for details. The class name is derived from the name of the table, and is postfixed by Meta. For example, for a table named sysApplInstallPkgTable in the MIB, mibgen will generate a Metadata class called SysApplInstallPkgTableMeta. 1.6.2 Class Containing the MBean View of the TableThe class containing the MBean view of a table enables you to add or remove entries dynamically from the table. This class contains callbacks and factory methods that enable you to instantiate or delete entries upon receiving requests from a remote SNMP manager. See the Simple SNMP Tables example and SNMP Table Insrtrumentation example in the Java Dynamic Management Kit 5.1 Tutorial for details. The class name is prefixed with Table, followed by the name of the table. For example, for a table named sysApplInstallPkgTable in the MIB, mibgen will generate an MBean view of the table class called TableSysApplInstallPkgTable. 1.6.3 Skeletal MBeans Representing SNMP Table EntriesFor each table in a MIB, the mibgen compiler generates an MBean that represents a table entry. These skeletal MBeans must be completed by adding implementation specific code, called access methods. The generated code is initialized with default values for table-entry fields. Therefore, if you compile the generated code directly, you obtain a running agent. In this case, values returned by the agent when querying the MIBs are not meaningful. The mibgen compiler uses the entry names that are specified in the MIB definition to name MBeans that are generated from table entries. For example, for a table entry definition named sysApplInstallPkgEntry in the MIB, mibgen will generate a skeletal MBean class named SysApplInstallPkgEntry and an interface named SysApplInstallPkgEntryMBean. Note - Remote creation of table entries is disabled by default, for security reasons. You can dynamically enable and disable remote creation of table entries by calling the setCreationEnabled operation on the generated MBean-like object. The RowStatus convention, that is defined in RFC 2579, is fully supported by the code generator. When a table is defined using SNMPv2, if it contains a control variable with row status syntax, the mibgen compiler generates a set of methods allowing this table to be remotely controlled by this variable. However, the remote creation and remote deletion of rows remains disabled by default. Table objects are divided into two categories:
When remote table-entry creation is enabled, and the creation of a new table is requested, a factory method is called on the MBean-like object to instantiate the new table entry. By default, an instance of the skeleton class for that table entry is instantiated.
|
public class g1 implements g1MBean, Serializable { protected Integer myVar = new Integer (1); public g1(SnmpMib myMib) { { public Integer getMyVar() throws SnmpStatusException { return myVar; } public void setMyVar(Integer x) throws SnmpStatusException { myVar = x; } } |
You must subclass or provide an implementation of the skeletal MBean to implement your MIB behavior. For information about developing an SNMP agent, SNMP Manager, SNMP API, and SNMP Proxy, see the corresponding sections in the Java Dynamic Management Kit 5.1 Tutorial.
![]() ![]() |