Administer > Transforming, loading, and extracting data > Overview of the data load utility


Workspace locking scenario using the Data load utility

When you load data into a workspace using the Data load utility, the locking policies defined for the workspaces is in effect. These scenarios describe the locking behavior when data is loaded into the workspace database.

The scenarios are based on the task group locking policy, which is the default locking policy for workspaces. When multiple task groups are involved, task group locking prevents potential inconsistencies where a managed asset is created or updated in one task group, and therefore cannot be updated again in a different task group at the same time.


Scenario 1

This scenario assumes that workspaces is already enabled, and two task groups (TG1 and TG2) are created.

Consider the following events within the same workspace:

  1. Use the data load utility, UserA loads some products under TG1.

  2. Before TG1 is completed, UserB tries to modify one of the products under TG2 in the Management Center.

Given these events, UserB cannot modify the products which are loaded through the data load utility by UserA because the products are locked by TG1. However, UserB can modify the products after TG1 is completed.


Scenario 2

This scenario assumes that workspaces is already enabled, and two task groups (TG1 and TG2) are created.

Consider the following events within the same workspace:

  1. Use the Management Center, userA modifies some product information such as the product description under TG1.

  2. Before TG1 is completed, UserB tries to update the same product description under TG2 using the data load utility.

Given these events, the data load utility throws an object lock exception because the product descriptions have been locked by TG1.


Scenario 3

This scenario assumes that workspaces is already enabled, and task group (TG1) is created.

Consider the following events within the same workspace:

  1. Use the Management Center, userA modifies some product information such as the product description under TG1.

  2. Before TG1 is completed, UserB tries 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 have been locked by TG1 in the workspace.


Ovveride workspace locking

If an object is locked by a workspace, the data load utility can override the locking by one of the following ways:

  1. Create a workspace that uses an emergency fix, and specify the workspaceIdentifier in the data load environment settings file. For more information about creating an emergency fix workspace, see Create a workspace.

  2. Add an override lock parameter in the data load utility configuration file. You can add the property attribute under the <_config:LoadOrder> element for all the load items in the wc-dataload.xml file. Or add the property to the <_config:BusinessObjectMediator> element in the individual business object configuration file as shown:

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


+

Search Tips   |   Advanced Search