Change workspaces locking policy

Do not change the workspaces locking policy if you have uncommitted data in any of your workspaces. This can cause undefined behavior with the uncommitted data.

(Developer) The development environment is not an authoring environment. Support is provided in the environment for customization purposes only. For example, testing changes to content management functionality. The ability to propagate changes is not available. To make changes to the content management workspaces, we cannot publish the changes out to another database. Before deciding on the locking policy to use on the authoring environment, review the Considerations when selecting a locking policy topic.

Procedure

1. Copy the following file to a temporary location:

   • (Developer) WCDE_installdir/xml/content-management/wc-resource-containers.xml

   • workspace_dir/WC/xml/content-management/wc-resource-containers.xml

   This file should never be directly modified.

2. Open the temporary copy of the file in a text editor.

3. Find the following text:

   <wc:DefaultConfiguration lockingPolicy="Workspaces_locking_policy"
                   enableDynamicWorkspaceCreation="false"
                   readPrefixName="WCR"
                   writePrefixName="WCW"
     />

4. For the locking policy to enable, replace Workspaces_locking_policy with one of the policy classes shown below the locking policy name:

   Option	Description
   Workspaces locking	com.ibm.commerce.context.content.locking.WorkspaceLockingPolicy
   Task group locking	com.ibm.commerce.context.content.locking.TaskGroupLockingPolicy
   Task locking	com.ibm.commerce.context.content.locking.TaskLockingPolicy
   No locking	com.ibm.commerce.context.content.locking.NoLockingPolicy

5. Save our changes.

6. Update the deployment package to include your updated files.

Related concepts
Authoring environment schema update tool
Workspaces locking policies
Workspaces object locking

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 retry for quick publish
Enable e-mail notification for workspaces
Enable shopping flow preview for workspaces

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
Catalog component
Considerations when selecting a locking policy