Configuration Options Related Tasks Related Topics
Use this page to configure an attribute change, which generates a trap immediately after an attribute in a configuration MBean is changed in any way.
Name | Description |
---|---|
Name |
The name of this attribute change. Each attribute change within a domain must have a unique name. The name displays in the Administration Console, and if you use WebLogic Server command-line utilities or APIs, you use this name to identify the attribute change monitor. After you create an attribute change, you cannot change its name. Instead, delete it and create a new one. MBean Attribute: Changes take effect after you redeploy the module or restart the server. |
Monitored MBean Type |
The MBean type that defines the attribute you want to monitor.
Do not include the WebLogic Server does not support using Attribute Change trap
notifications to monitor run-time attributes. Runtime MBeans always
include the word MBean Attribute: Changes take effect after you redeploy the module or restart the server. |
Monitored MBean Name |
The name of the MBean instance that you want to monitor. If you leave the name undefined, WebLogic Server monitors all instances of the MBean type that you specify in Monitored MBean Type. Do not enter the full JMX object name of the MBean instance.
Instead, enter only the value that you provided when you created
the instance. To create unique MBean object names, WebLogic Server
encodes several name-value pairs into each object name. One of
these pairs is In the previous example, specify MBean Attribute: Changes take effect after you redeploy the module or restart the server. |
Monitored Attribute Name |
The name of the attribute that you want to monitor. This attribute must be in the WebLogic Server MIB. MBean Attribute: Changes take effect after you redeploy the module or restart the server. |