Tune the performance of Quick publish

Aside from publishing workspace data to the Production environment database, quick publish also updates and marks all corresponding data in the production-ready schema STAGLOG table as processed. This process ensures that the data being quick published to the production database are not processed and published again during the next iteration of stagingprop. The process can take a long time to complete. If the database configuration meets certain criteria, we can tune the performance of quick publish by setting two optional attributes.


Task info

We can set the following configuration options to tune how the quick publish processes STAGLOG records:


Procedure

To tune quick publish performance:

  1. Change the configuration files below before building the application package with the WebSphere Commerce Build tool.

  2. Update the wc-resource-containers.xml file:

    1. Edit...

        WC_eardir\xml\content-management\wc-resource-containers.xml

    2. Locate the <wc:QuickPublishConfiguration> element, and add the postPublishSize parameter as shown:

        <wc:QuickPublishConfiguration>
        		<wc:Publisher className="com.ibm.commerce.context.content.resources.publish.DefaultJDBCContentPublisherImpl"
        		initParameters=[other-parameters] lowerCaseStaglog="true" updateStaglogStmtNum ="1" [other-parameters]/ >
        </wc:QuickPublishConfiguration>

  3. Save our changes and close the file.


Related tasks
Updating the quick publish target