Managing pureQuery client optimization in Web application environments, Part 1, Optimize applications on a single application server node

Tips for successful deployment

From the developerWorks archives

Charul Kapil, Jaijeet Chakravorty, and Manoj Sardana

Date archived: January 11, 2017 | First published: February 11, 2010

pureQuery client optimization requires the use of properties settings to enable a specific stage of the client optimization process. Settings for these properties vary, depending on the required behavior for your Web application environment. This first article of a two-part series describes property settings for a Web-based application running on a single application server node that uses single or multiple databases shared across multiple applications. The second article will focus on how to set client-optimization properties in more complex Web environments, such as with clustered servers. This article assumes you are familiar with the pureQuery client-optimization process and with setting Web application properties in WebSphere® Application Server or in your chosen application-server environment.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Information Management, Java development, Web development
ArticleID=467798
ArticleTitle=Managing pureQuery client optimization in Web application environments, Part 1: Optimize applications on a single application server node
publish-date=02112010