Configuration for tuning

After deployment to a production system, applications accept calls from real users (not test users), and the system generates call logs for each session that occurs. The logs represent a history of in-production performance, and are critical for gaining insight to application performance.

Application developers use the call logs (and call center reports from users and agents) to identify problems. The solution to a problem might involve a change to configuration, application logic, prompts, or communications between components (such as database interactions). Fixing problems with the configuration is the least expensive technique. No recompilation or deployment is needed. It is only necessary to keep a record of changes on the production system so they can be propagated to any mirrored systems, and replicated in the original development environment for future updates.

For an overview of the tuning lifecycle, see Tuning applications. The tuning mechanisms are the same as during application development (Configuration during application development).