(DB2)

Enable retry for quick publish

If quick publish fails because of a DB2 deadlock timeout error, the files and data changes do not get published. We can enable quick publish retry to automatically force quick publish to try again if a deadlock timeout exception is encountered.

Task info

When we enable quick publish for a task group, the changed files and data within the task group are published to production when all tasks are marked complete and all approvals are satisfied. However, if quick publish fails because of a DB2 deadlock timeout error, the file and data changes do not get published. We can enable quick publish retry to automatically force quick publish to try again when a deadlock timeout exception is encountered.

Procedure

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 element...
      <wc:QuickPublishConfiguration> element

      and add the retry and waitTime parameters as shown:

      <wc:QuickPublishConfiguration>
          <wc:Publisher className="com.ibm.commerce.context.content.resources.publish.DefaultJDBCContentPublisherImpl" 
              initParameters="batchSize=0" retry="5" waitTime="60"/>
      </wc:QuickPublishConfiguration>

      Note: batchSize refers to JDBC batch.

3. Update the wc-resource-containers.xsd file.

   1. Edit...
      WC_eardir\xml\content-management\xsd\wc-resource-contairs.xsd

   2. Locate the Publisher element, and add the retry and waitTime attributes as shown:

      <element name="Publisher">
        <complexType>
          <attribute name="className" type="string" use="required"/>
          <attribute name="initParameters" type="string" use="optional"/>
          <attribute name="retry" type="int" use="optional" form="unqualified">
            <annotation>
              <documentation>Number of times the content publisher should attempt the transaction again when it encounters a transaction rollback.</documentation>
            </annotation>
          </attribute>
          <attribute name="waitTime" type="int" use="optional" form="unqualified">
            <annotation>
              <documentation>Number of seconds the content publisher should wait between retry attempts.</documentation>
            </annotation>
          </attribute>
        </complexType>
      </element>

Related concepts
Authoring environment schema update tool

Related tasks
Enable Workspaces
Create an authoring environment
Synchronize an authoring environment with a production environment
Run the authoring environment update scripts on the WebSphere Commerce Server
Update the quick publish target
Update the JDBC provider setting for the quick publish target
Enable e-mail notification for workspaces
Enable shopping flow preview for workspaces
Change workspaces locking policy

Related reference
Ant target: CM_updateWorkspacesTable
Ant target: CM_updateWorkspacesSchema
Troubleshooting: Update Workspace failing to update the workspace because of missing column for primary key