Use The Diagnostic Cli - BEA WebLogic User Manual

Start Interception
1. Choose Settings → Interception to configure and start the interception.
2. Select the device type you want to target.
Note: For predictable results ensure you are using the appropriate browser. For example, if
you specify a WAP device but are using Internet Explorer as the browser, it will not display
the WAP content correctly.
3. Use your device to enter the address for the selected page. The request takes the form:
http://dc_host:dc_port/URL_request
where "dc_host" is the IP address of the machine where the Diagnostic Console is running,
"dc_port" is the port on which the Diagnostic Console is listening for requests (specified in
the Settings panel) for example, 4444. The "URL_request" is the name of file you are
investigating relative to the web application directory.
For example,
http://199.168.5.37:4444/requested_page.jsp
When the request reaches the Diagnostic Console, the response is displayed in the Response
View of the window. If the Diagnostics option is chosen, then the diagnostics messages will be
displayed in Diagnostics/Pre-transformed views.

Use the Diagnostic CLI

The Diagnostic Command-Line Interface (CLI) monitors WebLogic Mobility Server as it
processes multiple requests to applications. Use the CLI when you want to monitor requests being
made by several users — the Diagnostic Console monitors single requests only.
The Diagnostic Command-Line Interface provides a number of parameters that enable you to
track down performance or transformation issues. By default, the CLI reports all activity. You
can, however, specify a filter so that only activity that matches the specified filter is reported.
As you monitor WebLogic Mobility Server, it is likely that you will create a suite of diagnostic
tests, each with its own set of parameters. The CLI supports the use of parameter files — text files
containing a list of parameters — so you do not have to keep retyping the parameters from the
command line. You simply pass the parameter file when starting the CLI
See the end of the section for examples on how to use the CLI and to see some sample output.
Important note: The JVM on the client running the CLI must be the same version as on the
server running WebLogic Mobility Server.
Use the Diagnostic CLI with WebLogic
In a WebLogic deployment the Diagnostic CLI should be installed in, and invoked from, the
server environment. This tool uses Java Remote Method Invocation (RMI), which may have
implications for WebLogic users wanting to run this tool outside the production environment. If a
firewall infrastructure is in place, certain ports may need to be opened between the client running
the tool and the server. See the Java RMI documentation at http://java.sun.com/products/jdk/rmi/
for more information.
The Diagnostic CLI requires access to weblogic.jar via the CLASSPATH to support command
line diagnostics on WebLogic. This CLASSPATH is configured via the
property in
DiagnosticsTextUI.lax
.
BEA WebLogic Mobility Server User Guide - 139
Part VI Diagnostics
lax.class.path