WLDFResourceBean

Overview  |   Related MBeans  |   Attributes  |   Operations

Overview

The top of the WebLogic Diagnostic Framework (WLDF) module bean tree.

All WLDF modules have a WLDFResourceBean as their root bean (a bean with no parent). The schema namespace that corresponds to this bean is: http://www.bea.com/ns/weblogic/90.

Since 9.0.0.0    
Security roles The following roles have read, write, and invoke permission for all non-encrypted attributes and operations in this MBean:

  • Deployer
   
Fully Qualified Interface Name If you use the getMBeanInfo operation in MBeanTypeServiceMBean, supply the following value as this MBean's fully qualified interface name:
weblogic.diagnostics.descriptor.WLDFResourceBean
   
Factory Methods No factory methods. Instances of this MBean are created automatically.

Related MBeans

This section describes attributes that provide access to other MBeans. For more information about the MBean hierarchy, refer to WebLogic Server MBean Data Model.

 

Harvester

The Diagnostic Harvester configuration for this deployment.

Factory Methods No explicit creator method. The child shares the lifecycle of its parent.    
Privileges Read only    
Type WLDFHarvesterBean
Relationship type: Containment.

 

Instrumentation

The Diagnostic Instrumentation configuration for this deployment.

Factory Methods No explicit creator method. The child shares the lifecycle of its parent.    
Privileges Read only    
Type WLDFInstrumentationBean
Relationship type: Containment.

 

WatchNotification

The Diagnostic Watch and Notification configuration for this deployment.

Factory Methods No explicit creator method. The child shares the lifecycle of its parent.    
Privileges Read only    
Type WLDFWatchNotificationBean
Relationship type: Containment.

Attributes

This section describes the following attributes:

     

    Name of

    The name of the WebLogic Diagnostic Framework (WLDF) bean.

       
    Privileges Read only    
    Type java.lang.String
    Redeploy or Restart required Changes take effect after you redeploy the module or restart the server.