You can use Simple Network Management Protocol (SNMP) to provide monitoring data to enterprise-wide management systems. With SNMP, you configure agents to gather and send data about managed resources in response to a request from managers. You can also configure agents to issue unsolicited reports to managers when they detect predefined thresholds or conditions on a managed resource.
WebLogic Server SNMP agents query the WebLogic Server management system and communicate the results over the SNMP protocol. The WebLogic Server management system exposes management data through a collection of managed beans (MBeans). When a WebLogic Server SNMP agent receives a request from a manager, it determines which MBean corresponds to the OID in the manager’s request. Then it retrieves the data and wraps it in an SNMP response.
In each WebLogic Server domain, you can create multiple SNMP agents and organize them into a centralized or de-centralized model for SNMP monitoring and communication:
Note: To support domains that were created with WebLogic Server release 9.2 and earlier, you can enable and use the domain-scoped SNMP agent instead of configuring SNMP agents on the Administration Server or Managed Servers (server SNMP agents). The domain-scoped agent offers the same features as the server SNMP agent in the centralized model described above. However, its underlying implementation is different and it will eventually be deprecated. The domain-scoped agent is overridden if you target a server SNMP agent to the Administration Server.
You can also use WebLogic Server SNMP agents to collect SNMP requests from various network resources and forward them to other SNMP agents. See Create SNMP proxies.
You cannot use SNMP to change the configuration of a domain.
To request data about a specific managed resource, a manager must be able to uniquely identify the resource. In SNMP, each managed resource is described in a Management Information Base (MIB) module as a managed object with a unique object identifier (OID). Both manager and agent must have access to the same MIB module to communicate about specific managed resources.
For information about loading a MIB module, refer to the documentation that the vendors of your SNMP managers supply.
A trap destination contains the information that the SNMP agent needs to send notifications to an SNMP manager.