BMC Software, Inc., Confidential and Proprietary Information
Managing the BEA WebLogic Environment 4-11
Generating Reports
PATROL for BEA WebLogic provides a number of reporting functions to
list various configuration settings and performance metrics. These reports
are always displayed in a system output window. See “Generating a
Report” on page 4-13 if you do not know how to use the reporting
commands.
Table 4-2 lists the basic types of reports you can generate and describes
what type of information will be produced by each. If you enable the
advanced monitoring instrumentation and profiling features, additional
reports on J2EE object performance will be available. These are
described in Chapter 9, “Instrumenting and Profiling J2EE Components”
on page 9-1.
Table 4-2 Reports in PATROL for BEA WebLogic (Part 1 of 2)
Report Name
From Instance
Icon of Class... Contents
Connection Leak JDBC displays connection leak profile, including stack trace at the
time the connection was created
Execute Threads
Report
EXEC_QUEUE provides usage and activity info for all threads in an
execution pool; includes current request, last request,
number of requests served, current user, and a flag
indicating whether the thread is idle.
JMS Server
Components
SERVER configurable reports on JMS runtime data, such as
connection factories, templates, destination keys, file store,
JDBC store, or servers
JNDI Report SERVER provides directory mapping information for various aspects
of the WebLogic system, such as file system, EJB, JDBC,
server, RMI, JMS, transaction, and common
JTA Information SERVER provides statistics on the Java Transaction subsystem,
including total transactions and total rollbacks
JTA Transaction SERVER provides transaction information (such as number of
transactions committed, rolled back, heuristics) organized
by name, resource, or current transactions (in-flight)
