Scenarios: Workspace locking for the Data Load utility

When we use the Data Load utility to load data into a workspace, the locking policies that are defined for the workspace are in effect. These locking policies affect the loading of data into the workspace database.

The workspace locking scenarios are based on the task group locking policy, which is the default locking policy for a workspace. When multiple task groups are involved, task group locking prevents potential inconsistencies. For example, when a managed asset is created or updated in one task group, the managed asset cannot be updated simultaneously in a different task group.


Scenario 1

This scenario assumes that workspaces are enabled and that two task groups (TG1 and TG2) exist. Consider the following events within the same workspace:

  1. While UserA uses the Data Load utility, they load products under the task group TG1.

  2. Before the TG1 task group is completed, UserB attempts to modify products included in TG1 with the task group TG2.

Given these events, UserB cannot modify the products which UserA is loading with the Data Load utility. These products are locked by the TG1 task group. UserB can modify the products after the TG1 task group is completed.


Scenario 2

This scenario assumes that workspaces are enabled and that two task groups (TG1 and TG2) exist. Consider the following events within the same workspace:

  1. Use Management Center, UserA modifies product information such as product descriptions under the task group TG1.

  2. Before the TG1 task group is completed, UserB attempts to update the same product descriptions under the TG2 task group using the Data Load utility.

Given these events, the Data Load utility throws an object lock exception because the product descriptions are locked by the task group TG1.


Scenario 3

This scenario assumes that workspaces are enabled, and the task group (TG1) exists. Consider the following events within the same workspace:

  1. Use Management Center, UserA modifies product information such as product descriptions under the task group TG1.

  2. Before the task group TG1 is completed, UserB attempts to update the same product description using the Data Load utility without specifying any workspace parameters.

Given these events, the Data Load utility throws an object lock exception because the product descriptions are locked by the task group TG1 in the workspace.


Overriding workspace locking

If an object is locked by a workspace, we can use the Data Load utility to override this locking with one of the following methods:

  1. Create a workspace that uses an emergency fix, and specify the workspace identifier in the data load environment configuration file.

  2. Add an override lock property in the data load order configuration file. We can add this property within the <_config:LoadOrder> element for all of the load items in the wc-dataload.xml data load order configuration file. We can also add this property within the <_config:BusinessObjectMediator> element in the business object configuration file. We can specify this property with the following format: 

      <_config:property name="workspaceLockOverride" value="true" />