Getting Startedwith pureQuery

Chapter 8 – Extended Insight 163
• ResultSet processing time (aggregated application time from query execution
through ResultSet close for a particular query and client user)
• Driver time (aggregated, accumulated time spent in the IBM driver for a particular
statement and client user - includes open, fetch and close cursor times for queries,
and execute time for non-queries)
• Network time (aggregated, accumulated time spent in the network per statement
and client user)
• Server time (aggregated, accumulated execution time reported by the server for a
particular statement and client user)
Additional detailed information is also available about each client, such as a breakdown of
transaction times for the client, information about negative SQL codes, and certain
Websphere Application Server statistics, such as connection pool wait times (minimum
level of WAS required). See the OPM documentation for the complete set of information
available for client monitored workloads.
8.4.2 Monitoring pureQuery Applications associated with pureQueryXml
Several types of applications are associated with application metadata in the form of
pureQueryXml. These include pureQuery annotated method style applications,
applications resulting from any pureQuery integrated tooling that generates pureQueryXml
(such as Data Web Service (DWS) applications or WAS/JPA pureQuery applications), and
Client-Optimized JDBC or CLI applications. See Chapter 11 , Chapter 16 , and Chapter 6
for more information about creating these types of applications.
Extended Insight collects the same statistics for pureQuery applications associated with
pureQueryXML, as it does for plain JDBC or CLI applications. In addition, for most
applications associated with pureQueryXml, Extended Insight also identifies the
pureQueryXml element associated with the executing statement. This means that when
the pureQueryXml is registered with OPM and Extended Insight monitoring is enabled, a
DBA can use the monitoring tools to easily identify additional information about a
pureQuery statement associated with pureQueryXml. For generated or tooling-produced
pureQueryXml, this information includes:
• Source class
• Source timestamp (version)
• Source line of code containing the given SQL string
For client optimized applications executing or loading captured SQL from pureQueryXml
(see Chapter 6 for the variety of configurations under which pureQuery Client Optimization
executes captured SQL), this information includes:
• pureQueryXml file version