Loading data from an external source into workspaces with the mass load utility

You can load data and files from an external source into your workspaces with the mass load utilities.

Feature Pack 6 or later The massload utility is deprecated for WebSphere Commerce Version 7 Feature Pack 6. The Data Load utility is the recommended command-line loading utility. If you are currently using the mass load utility, you are recommended to switch to the Data Load utility to load your CSV and XML input files into your target database. If your system contains scheduled and automated processes that use massload, it is recommended that you update these processes to use the Data Load utility. Other WebSphere Commerce utilities that use the massload utility, such as the acpload utility, continue to use the massload utility in WebSphere Commerce Version 7 Feature Pack 6. If you have business reasons to continue using the massload utility, you can continue to use this utility. For more information about the Data Load utility, see Overview of the Data Load utility. You can switch to the Data Load utility by using the TableObjectMediator to load your data when no business object mediator exists for the data that you are loading. For more about the TableObjectMediator formation, see Data Load utility table-based mediator and builder.

Only data that resolves into managed assets is loaded into workspaces. Any data that resolves into non-managed assets is loaded into the production-ready data on the authoring server.

If you load bad data into a workspace, run the mass load utility with the same XML input file and specifying the delete method. This loading removes the bad data from the workspace. After that, you can correct the data and try to load the data into the workspace again.

When loading data and files into workspaces with the loading utilities, take note of the following considerations:

The loading utilities load all data that resolves into managed assets into workspaces. Any data that resolves into non-managed assets loads into the production-ready data on the authoring server.
The loading utilities do not observe the WebSphere Commerce database referential constraints when you load data into a workspace. This limitation in workspaces permits bad data to be loaded into the workspace. Bad data in the workspace prevents the workspace data from being committed to the production-ready data.

Procedure

Ensure that you completed the following configuration tasks on the authoring server:
If this is the first time that the data is being loaded, generate a DTD and schema for use with the loading utilities.
If you have not already resolved identifiers, resolve them now.
Run the massload utility to load data into the workspace.
Run the fileloader utility to load managed files into the workspace.