After you create an attribute change, you assign (target) it to one or more server instances. The attribute change looks for changes in attribute values only on the servers to which it has been targeted.
Note: To temporarily stop an attribute change from generating traps, un-target it from all servers by deselecting them on the Servers tab.
To target attribute changes:
Note: When you assign an attribute change to a server, you deploy a JMX listener and filter to the server. The listener forwards a notification to the WebLogic SNMP agent only if an event matches the criteria in the attribute change.
For example, if you create an
attribute change that observes the
attribute of ServerA's
MBean, and if you target this attribute change to
ServerB, the attribute change on ServerB will never
generate a trap, because ServerB does not have
access to the configuration data of