Change the workspaces locking policy

The development environment is not meant to be an authoring environment. Support is provided in the environment for customization purposes only. For example, testing out changes to the content management functionality, and for simple tests, such testing out how the function works for the very first time. The ability to push out changes is not available. If you want 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 your authoring server, review the
Considerations when selecting a locking policy topic carefully to understand the implications of each locking policy.

Do not change the workspaces locking policy if you have uncommitted data in any of your workspaces.

To change the workspaces locking policy in WebSphere Commerce Developer:

  1. Open the following file in a text editor:

  2. Find the following text: 
    <wc:DefaultConfiguration
                        lockingPolicy="
Workspaces_locking_policy"
                        enableDynamicWorkspaceCreation="false"
                        readPrefixName="WCR"
                        writePrefixName="WCW"
                />

  3. For the locking policy you want to enable, replace Workspaces_locking_policy with the policy class shown below the locking policy name:

    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

  4. Save your changes.

  5. Stop and restart WebSphere Commerce.

Related concepts

Workspaces

Workspaces locking policies

Related tasks

Create an authoring server

Start and stopping WebSphere Commerce