14-2 Configuring and Using the Diagnostics Framework for Oracle WebLogic Server
descriptor file with the application archive in the ARCHIVE_PATHMETA-INF directory for the deployed application. For example:
D:\bea\wlserver_ 10.3\samples\server\medrec\dist\standalone\exploded\medrec\META-INF\weblogic-diagn
ostics.xml
You can deploy the diagnostic module in both exploded and unexploded archives.
You can use any of the standard WebLogic Server tools provided for controlling deployment, including the WebLogic Administrative Console or the WebLogic
Scripting Tool WLST.
For information on creating modules and deploying applications, see Deploying Applications to Oracle WebLogic Server.
Because of the different ways that diagnostic application modules and diagnostic system modules are deployed, there are some differences in how you can reconfigure
them and when those changes take place, as shown in Table 14–2
. The details of how to work with diagnostic application modules is described throughout this section. See
Chapter 11, Configuring Instrumentation, for information about working with
diagnostic system modules.
14.2 Using Deployment Plans to Dynamically Control Instrumentation Configuration
WebLogic Server supports deployment plans, as specified in the J2EE Deployment Specification API JSR-88. With deployment plans, you can modify an applications
configuration after the application is built, without having to modify the application archives. For complete documentation on using deployment plans in WebLogic
Server, see Configuring Applications for Production Deployment in Deploying Applications to Oracle WebLogic Server.
Note: If the EAR archive contains WAR, RAR or EJB modules that
have the weblogic-diagnostics.xml descriptors in their META-INF directory, those descriptors are ignored.
Table 14–1 Comparing System and Application Modules
Monitor Type AddRemove
Objects Dynamically
AddRemove Objects with
Console Modify with
JMX Remotely
Modify with JSR-88
non-remote
Modify with Console
System Module
Yes Yes
Yes No
Yes - via JMX Application
Module Yes, when hot
swap
1
is enabled
No, when hot swap is not
enabled: module must
be redeployed
1
See Section 14.2, Using Deployment Plans to Dynamically Control Instrumentation Configuration,
for information about hot swap.
Yes No
Yes Yes - via plan
Deploying WLDF Application Modules 14-3
If you want to reconfigure an application that was deployed without a deployment plan, you must undeploy, unarchive, reconfigure, re-archive, and then redeploy the
application. With a configuration plan, you can dynamically change many configuration options simply by updating the plan, without modifying the application
archive.
If you enable a feature called hot swap see Section 14.6, Enabling Hot-Swap
Capabilities before deploying your application with a deployment plan, you can
dynamically update all instrumentation settings without redeploying the application. If you do not enable hot swap, or if you do not use a deployment plan, changes to
some instrumentation settings require redeployment, as shown in Table 14–2
.
You can use a deployment plan to dynamically update configuration elements without redeploying the application.
■
enabled
■
dye-filtering-enabled
■
dye-mask
■
action
14.3 Using a Deployment Plan: Overview
