WebSphere Commerce Version 7.0.0.6 or later

Stagingprop utility considerations

Updating the stagingprop utility for your site can improve the performance of certain promotion-related processes for your site. Updating this utility can reduce database connections, improve SQL optimization, speed up record consolidation and provide more reporting of processes

1Installing WebSphere Commerce Fix Pack 6 or later, can provide your site with a better-performing stagingprop utility. Updating this utility can reduce the number of database connections, run better optimized SQL, and provide faster consolidation of records in the STAGLOG table. A summary report is included to indicate the number of records that are processed. This report details the records according to tables and transaction types (Insert/Update/Delete). This report can help your site IT staff better understand the effect of business user traffic on the staging processes.

This stagingprop utility update improves the following behavior and functionality:
  • Improving stagingprop performance. With this update, the stagingprop utility can reduce the number of database input and output operations by increasing the number of records fetched at a time. This update also adds a database index on the STAGLOG table that provides improved fetch performance.
  • Improving error toleration with the addition of -actionOnError support for operations that are performed on the same record. This -actionOnError parameter defines how the stagingprop utility proceeds when the utility encounters these errors. The update adds support for stagingprop to tolerate errors and continue to propagate data instead of exiting the propagation process. This update adds error toleration support for stagingprop when the utility encounters the following operations on the same record:
    • Deletion followed by Update
    • Deletion followed by Deletion
    • Insertion followed by Insertion
    • Update followed by Insertion
  • Providing support for the cyclic reuse of unique keys. This reuse is provided by the addition of support through the addition of the column UPDATABLE_UK_COL in the database tables STGSITETAB and STGMERTAB.
  • Improving problem determination by providing distinct value exit codes when the utility encounters errors. These exit codes can be used to categorize the severity of errors and to determine the phase of the utility at which any errors were encountered. An exit code of 0 indicates a successful execution. An exit code other than 0 is an indication of an error that is encountered by the utility. You can review the log file that is generated by the utility for the diagnostic information that is recorded when a non-zero exit code is issued by the utility. For more information about these codes, see stagingprop exit codes.
1 The interim fix for APAR JR42158 includes this function.