Administer > Manage WebSphere Commerce features > Workspace Administration Tool > Workspaces locking policies


Changing workspaces locking policy

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

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, you cannot publish the changes out to another database. Before deciding on the locking policy to use on the authoring server, review the Considerations when selecting a locking policy topic carefully to understand the implications of each locking policy.


Procedure

  1. Copy the following file to a temporary location:

    • WCDE_INSTALL/xml/content-management/wc-resource-containers.xml

    • WC_EAR/xml/content-management/wc-resource-containers.xml

    This file should never be directly modified. For more information, refer to XML configuration directory.

  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 the changes.

  6. Update WebSphere Commerce with the updated file. See the Update applications topic in the WebSphere Application Server Information Center for instructions. 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

    This step only applies to the WebSphere Commerce runtime environment.

  7. Stop and restart WebSphere Commerce.


+

Search Tips   |   Advanced Search