edocs Home > Oracle WebLogic Server Documentation > Administration Console Online Help > Configure

Configure diagnostic profiling for a JDBC data source

If the monitoring statistics that you are seeing indicate that there is a problem in your WebLogic Server domain, you can configure any data source to collect profile information to help you pinpoint the source of the problem. The collected profile information is stored in records in the WLDF Archive.

To configure diagnostic profiling for a JDBC data source:

1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).

2. Navigate to the data source that you want to modify:

   • Navigate to JDBC data source system resources

   • Navigate to JDBC application modules

3. Select the Configuration: Diagnostics tab.

4. Enable any of the following diagnostic profiling options:

   • Profile Connection Usage

   • Profile Connection Reservation Wait

   • Profile Connection Leak

   • Profile Connection Reservation Failed

   • Profile Statement Cache Entry

   • Profile Statement Usage

   • Profile Connection Last Usage

   • Profile Connection Multithreaded Usage

5. Configure how frequently the selected profiling options should occur:

   • Profile Harvest Frequency Seconds

   • Frequency Interceptor

   See Configuration Options for more information.

6. Click Save.

7. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
   Not all changes take effect immediately—some require a restart (see Use the Change Center).

} } (document.images){ dcs_imgarray[dcs_ptr] = new Image; dcs_imgarray[dcs_ptr].src = dcs_src; WT[myMeta.name.substring(3)]=myMeta.content; } if DCSext[myMeta.name.substring(7)]=myMeta.content; } } } } for (N in DCS){P+=A( N, DCS[N]);} for (N in WT){P+=A( "WT."+N, WT[N]);} for (N in DCSext){P+=A( N, DCSext[N]);} //} aCrumb=aCookie[i].split("="); if (crumb==aCrumb[0]){ return aCrumb[1]; } } return null; } i=0;i