Changing 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.

Procedure
-
Copy the following file to a temporary location:
WCDE_installdir/xml/content-management/wc-resource-containers.xml
- WC_eardir/xml/content-management/wc-resource-containers.xml
- Open the temporary copy of the file in a text editor.
-
Find the following text:
<wc:DefaultConfiguration lockingPolicy="Workspaces_locking_policy" enableDynamicWorkspaceCreation="false" readPrefixName="WCR" writePrefixName="WCW" />
-
For the locking policy you want 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
- Save your changes.
-
Update WebSphere Commerce with the updated file. For more information, see the Updating enterprise application files topic. Ensure that you follow the instructions for updating a
single file.
You will need the following information:
- Enterprise application name
- WC_enterprise_application
- Relative path to file
- xml/content-management/wc-resource-containers.xml
Note: This step only applies to the WebSphere Commerce runtime environment. - Stop and restart WebSphere Commerce.