WebLogic Server Command Reference
Returns a description of the managed object that immediately follows one or more OIDs that you specify.
Instead of the recursive listing that the snmpwalk
command provides, this command returns the description of only the one managed object whose OID is the next in sequence. You could string together a series of snmpgetnext
commands to achieve the same result as the snmpwalk
command.
If you specify an object type, this command returns the first instance of the object type, regardless of how many instances of the type exist.
To see the WebLogic Server MIB tree, refer to the WebLogic Server SNMP MIB Reference. For information about the structure of the MIB and its object identifiers (OIDs), refer to "Object Identifiers" in WebLogic SNMP Management Guide.
java snmpgetnext [-d] [-v (v1,v2)] [-c
snmpCommunity
] [-psnmpPort
]
[-ttimeout
] [-rretries
]host
OID
[OID
]...
For information about the command arguments that are not listed in the above table, refer to Table 6-1.
The following example retrieves the name of an application that has been deployed on the Administration Server. The OID in the example command is for the applicationRuntimeName
object type, which represents the Name
attribute of the applicationRuntime
MBean.
java snmpgetnext localhost .1.3.6.1.4.1.140.625.105.1.15
If you invoke this command from a computer that is running the example MedRecServer, the command returns output similar to the following:
Response PDU received from /127.0.0.1, community: public
Object ID: .1.3.6.1.4.1.140.625.105.1.15.32.49.102.98.97.100.97.102.99.57.48.50.
102.48.98.53.54.100.100.49.54.50.54.99.54.99.49.97.97.98.53.100.97
STRING: MedRecServer_uddiexplorer
To determine whether there are additional applications deployed on the Administration Server, you can use the output of the initial snmpgetnext
command as input for an additional snmpgetnext
command:
java snmpgetnext localhost .1.3.6.1.4.1.140.625.105.1.15.32.49.102.98.97.100.97.102.99.57.48.50.102.
48.98.53.54.100.100.49.54.50.54.99.54.99.49.97.97.98.53.100.97
The command returns output similar to the following:
Response PDU received from /127.0.0.1, community: public
Object ID: .1.3.6.1.4.1.140.625.105.1.15.32.54.98.49.101.57.56.54.98.98.50.57.10
0.54.55.48.100.56.98.101.101.97.55.48.53.57.99.49.51.56.98.97.99
STRING: MedRecServer_StartupEAR
The following example specifies two OIDs to retrieve the name of an application that has been deployed on the Administration Server and the name of a JDBC connection pool. The OIDs in the example command are for the applicationRuntimeName
object type, which represents the Name
attribute of the ApplicationRuntime
MBean, and jdbcConnectionPoolRuntimeName
, which represents the Name
attribute of the JDBCConnectionPoolRuntimeMBean
.
java snmpgetnext localhost .1.3.6.1.4.1.140.625.105.1.15
.1.3.6.1.4.1.140.625.190.1.15
If you invoke this command from a computer that is running the example MedRecServer, the command returns output similar to the following:
Response PDU received from /127.0.0.1, community: public
Object ID:
.1.3.6.1.4.1.140.625.105.1.15.32.49.102.98.97.100.97.102.99.57.48.50.
102.48.98.53.54.100.100.49.54.50.54.99.54.99.49.97.97.98.53.100.97
STRING: MedRecServer_uddiexplorer
Object ID:
.1.3.6.1.4.1.140.625.190.1.15.32.53.53.49.48.50.55.52.57.57.49.99.102
.55.48.98.53.50.54.100.48.100.53.53.52.56.49.57.49.49.99.99.99
STRING: MedRecPool-PointBase