14-4 Configuring and Using the Diagnostics Framework for Oracle WebLogic Server
3.
Create a deployment plan, for example by using weblogic.PlanGenerator. See Section 14.4, Creating a Deployment Plan Using weblogic.PlanGenerator.
4.
Start the server, optionally enabling hot-swap capability. See Section 14.6,
Enabling Hot-Swap Capabilities.
5.
Deploy the application using the deployment plan. See Section 14.7, Deploying an
Application with a Deployment Plan .
6.
When needed, edit the plan and update the application with the plan. See Section 14.8, Updating an Application with a Modified Plan.
14.4 Creating a Deployment Plan Using weblogic.PlanGenerator
You can use the weblogic.PlanGenerator tool to create an initial deployment plan, and interactively override specific properties of the weblogic-diagnostics.xml descriptor.
The PlanGenerator tool inspects all J2EE deployment descriptors in the selected application, and creates a deployment plan with null variables for all relevant
WebLogic Server deployment properties that configure external resources for the application.
To create the plan, use the following syntax: java weblogic.PlanGenerator -plan output-plan.xml [options]
application-path For example:
java weblogic.PlanGenerator -plan foo.plan -dynamics testappsmywar
For more information about creating and using deployment plans, see Configuring Applications for Production Deployment in Deploying Applications to Oracle WebLogic
Server.
For more information about using PlanGenerator, see weblogic.PlanGenerator Command Line Reference and Exporting an Application for Deployment to New
Environments in Deploying Applications to Oracle WebLogic Server
14.5 Sample Deployment Plan for Diagnostics
Example 14–1 shows a simple deployment plan generated using
weblogic.PlanGenerator. For readability, some information has been removed. The plan enables the Servlet_Before_Service monitor and attaches to it the actions
DisplayArgumentsAction and StackDumpAction.
Example 14–1 Sample Deployment Plan
?xml version=1.0 encoding=UTF-8? deployment-plan xmlns=http:xmlns.oracle.comweblogicweblogic-diagnostics
xmlns:xsi=http:www.w3.org2001XMLSchema-instance global-variables=false
application-namejsp_expr_rootapplication-name
Note: The -dynamics options specifies that the plan should be
generated to include only those options that can be dynamically updated.
Deploying WLDF Application Modules 14-5
variable-definition -- Add two additional actions to Servlet_Before_Service monitor --
variable nameWLDFInstrumentationMonitor_Servlet_Before_Service_Actions_113050559713922name
valueDisplayArgumentsAction,StackDumpActionvalue variable
-- Enable the Servlet_Before_Service monitor -- variable
nameWLDFInstrumentationMonitor_Servlet_Before_Service_Enabled_113050559713927name valuetruevalue
variable variable-definition
module-override module-namejspExpressionWarmodule-name
module-typewarmodule-type module-descriptor external=false
root-elementweblogic-web-approot-element uriWEB-INFweblogic.xmluri
module-descriptor module-descriptor external=false
root-elementweb-approot-element uriWEB-INFweb.xmluri
module-descriptor module-descriptor external=false
root-elementwldf-resourceroot-element uriMETA-INFweblogic-diagnostics.xmluri
variable-assignment nameWLDFInstrumentationMonitor_Servlet_Before_Service_Actions_113050559713922name
xpathwldf-resourceinstrumentationwldf-instrumentation-monitor[name=Servlet_Before_ Service]actionxpath
variable-assignment variable-assignment
nameWLDFInstrumentationMonitor_Servlet_Before_Service_Enabled_113050559713927name xpathwldf-resourceinstrumentationwldf-instrumentation-monitor[name=Servlet_Before_
Service]enabledxpath variable-assignment
module-descriptor module-override
config-root xsi:nil=trueconfig-root deployment-plan
For a list and documentation of diagnostic monitors and actions that you can specify in the deployment plan, see
Appendix B, WLDF Instrumentation Library.
14.6 Enabling Hot-Swap Capabilities
