BEA WebLogic User Manual page 146

Part VI Diagnostics
Use Parameter Files
Rather than typing in a long list of parameters, you can save time and effort by storing your
parameters in a file and passing this file to the Diagnostic CLI. For an example, see "Example 2:
Use a Parameter File" later in this section.
Parameter files are plain text files, with each parameter on a separate line. The file can contain all
parameters except the username and password.
There are two ways to use parameter files:
•
–paraminfile file: Specify a file containing the parameters to be read in
•
–paramoutfile file: Specify a file to capture the parameters you enter on the command line.
This file can be subsequently used to read in the parameters.
Filter Content
By default, CLI monitors and reports on all activity. However, you can use the -filter parameter to
listen for and report on specific activity, thereby screening everything else out. For example, you
can choose to listen for activity relating to a specific URL
Filtering Content
To display messages:
For a specific request header
For a specific unique request
header that matches selected
value
Containing a specific request
parameter
For a specific unique request
parameter that matches the
selected value
For a particular URL
Specify Diagnostic Messages
Specify, at the end of the command line, the diagnostic messages (topics) you want to listen to.
Additionally, you can specify whether you want normal or verbose output. A full list of topics is
described in the section.
Example: MIS.Client verbose
142 - BEA WebLogic Mobility Server User Guide
Specify this FILTER option:
requestHeader:<headerName>
uniqueRequestHeader:<headerName>
requestParameter:<paramName>=<value>
uniqueRequestParameter:<paramName>
url:<value>