Fix Pack 3 for ODS and pureQuery delivers key enhancements for pureQuery client optimization
IBM_Optim 27000269HS Visits (2558)
I talk to many, many people about pureQuery and the benefits it can bring to performance, security, and problem determination of database applications. A key part of being able to deliver these enhancements to the wide variety of existing Java applications is the ability to layer pureQuery optimization onto existing applications without making changes to the application code. This process is called client optimization.
We have some enterprise customers now reaping the benefits of client optimization leading to this delivery which helps further improve security, manageability, and scalability to support complex enterprise environments. The main result of these requirements is delivery of a shared repository that can be used to securely store pureQuery artifacts. Not only does this provide added security, it provides the DBA with centralized control of the client optimization process. In other words, after the initial pureQuery Runtime setup within the application server by the administrator, you, the DBA, can modify the application’s pureQuery Runtime environment configuration without requiring further changes to the application server.
In addition, the centralized repository makes it possible to do continuous capturing, providing a step toward the vision of a more automated capture, configure, and bind process.
Another enhancement based on customer requests is the ability to group SQL into packages based on string tokens or special register values to streamline and simplify package management. An example of where this can be useful is if you are currently using special registers to set the schema qualifier during dynamic execution. Now you can package up the appropriate SQL statements into separate packages (one per schema for example) and do the same thing statically using the QUALIFIER BIND option.To help make sense of these enhancements, the product documentation for client optimization has been updated with scenario-based guidance on running, deploying, managing, and troubleshooting the client optimization process.
If you are interested in hearing more about the capabilities in this release from product experts, I invite you to join us on June 24th for the Virtual Tech Briefing entitled pureQuery Deep Dive Part 3: Client optimization administration. My colleagues Patrick Titzler and Chris Farrar, who some of you may remember from the first pureQuery deep dive tech briefing, will provide and overview of the new capabilities, how it fits into the overall direction we’re going, and will be available to answer questions. Patrick is planning also to do some demos of the tooling support for these features delivered in the Optim Development Studio Fix Pack 3.