Getting Startedwith pureQuery
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter 8 – Extended Insight 161<br />
It’s possible to improve this situation by executing static applications (see Appendix C<br />
Static SQL to learn more), or if client applications are configured to use DB2 driver client<br />
properties (for example, by using one of the JDBC 4.0 API’s setClientInfo(String<br />
name, String value) or setClientInfo(Properties properties) methods on the<br />
active connection). Otherwise, the DBA monitoring the workload will still have trouble<br />
identifying the dynamic application executing a given SQL statement. Yet this is often<br />
exactly what is required to resolve the problem. Extended Insight together with <strong>pureQuery</strong><br />
application metadata provide a more reliable way to address this issue and result in quicker<br />
problem resolution times for <strong>pureQuery</strong> applications.<br />
8.3.2.1 <strong>pureQuery</strong>Xml Speeds Problem Resolution<br />
<strong>pureQuery</strong> applications such as Client Optimized JDBC or CLI applications, <strong>pureQuery</strong><br />
annotated method style applications, <strong>pureQuery</strong> Data Web Services, or applications<br />
created using the Websphere JPA / <strong>pureQuery</strong> integration solution, all produce a set of<br />
<strong>pureQuery</strong> application metadata called <strong>pureQuery</strong>Xml. <strong>pureQuery</strong> application metadata is<br />
stored in an xml file, and describes a set of SQL statements and their source. It is created<br />
during the capture and configure phase for Client Optimized applications, and during the<br />
development phase for <strong>pureQuery</strong> applications developed using Optim Development<br />
Studio.<br />
<strong>pureQuery</strong> tooling provides the capability to register <strong>pureQuery</strong>Xml with Optim<br />
Performance Manager using the ManageRepository tool. To maximize the problem<br />
determination effectiveness of OPM EI, it is important to register the new <strong>pureQuery</strong>Xml<br />
with OPM when a new version of a <strong>pureQuery</strong>Xml-associated application is deployed in the<br />
enterprise. Registering <strong>pureQuery</strong>Xml with OPM makes it easier to monitor and perform<br />
problem determination throughout the enterprise, and it is an important deployment step<br />
that ties together all stages of the application lifecycle. For example, registered metadata<br />
makes it easier for a DBA who is monitoring an SQL statement to identify the application<br />
type and application version executing that statement.<br />
Figure 8.6 shows the lifecycle process that maximizes the capability of Optim tooling to<br />
improve application lifecycle management. The application developer/system administrator<br />
registers a set of <strong>pureQuery</strong> application metadata with OPM for each deployed <strong>pureQuery</strong><br />
application in the enterprise. This improves the ability of the database administrator using<br />
OPM for real-time monitoring to quickly identify problem applications, and integrates key<br />
information throughout the lifecycle to improve communication and speed up problem<br />
resolution:
Change language